System and method for simplified data transfer

ABSTRACT

Systems and methods of performing a simplified data transfer are provided. For example, a simplified data transfer system may include two or more devices configured to perform a simplified data transfer. The first device may be configured to save and transfer data associated with applications open on the first device. When the second device initiates communication, the first device may automatically send the open application data to the second device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 12/286,398, filed on Sep. 30, 2008, which is anon-provisional of and claims priority to U.S. Provisional PatentApplication No. 61/059,804, filed on Jun. 8, 2008. The entire contentsof both patent applications are hereby incorporated by reference.

BACKGROUND

1. Technical Field

The present disclosure relates generally to transferring informationbetween electronic devices and, more particularly, to transferringinformation via one or more electronic devices in a simplified manner.

2. Description of the Related Art

This section is intended to introduce the reader to various aspects ofart that may be related to various aspects of the present disclosure,which are described or claimed below. This discussion is believed to behelpful in providing the reader with background information tofacilitate a better understanding of the various aspects of the presentdisclosure. Accordingly, it should be understood that these statementsare to be read in this light, and not as admissions of prior art.

Electronic devices may be capable of running applications for displayingand manipulating data. As such, a first electronic device may be able todisplay, manipulate, or store data from a second electronic device,provided that the data is transferred from the second device to thefirst device. Though a user may have access to two similarly capableelectronic devices, sharing data between the two devices may involve anumber of steps, each of which may vary in difficulty. The process oftransferring data between the devices may include many user decisions,such as which data to save, where the data is saved, which formats eachdevice may be capable of processing, how to interconnect the devices fora most effective data transfer, etc. Such complexity may increase thedifficulty or time spent transferring data between two electronicdevices.

SUMMARY

Certain aspects commensurate in scope with the disclosed embodiments areset forth below. It should be understood that these aspects arepresented merely to provide the reader with a brief summary of certainforms the disclosure might take and that these aspects are not intendedto limit the scope of the disclosure. Indeed, the disclosure mayencompass a variety of aspects that may be set forth below.

Systems and methods of performing a simplified data transfer areprovided. For example, a simplified data transfer system may include twoor more devices configured to perform a simplified data transfer. Thefirst device may be configured to save and transfer data associated withapplications open on the first device. When the second device initiatescommunication, the first device may automatically send the openapplication data to the second device.

A method of performing the simplified data transfer may includeinitiating communication using near field communication (NFC) betweentwo devices. Next, data associated with open applications on one of thetwo devices may be saved and then transferred to the other. Transferringthe data may take place using a peer-to-peer connection other than viaNFC.

BRIEF DESCRIPTION OF THE DRAWINGS

Advantages of the disclosure may become apparent upon reading thefollowing detailed description and upon reference to the drawings inwhich:

FIG. 1 is a block diagram illustrating an embodiment of an electronicdevice 10 configured for simplified data transfer;

FIG. 2 is a schematic of a handheld device representing an embodiment ofthe electronic device of FIG. 1;

FIG. 3 is a schematic of a computer representing an embodiment of theelectronic device of FIG. 1;

FIG. 4 is a schematic of a standalone media player representing anembodiment of the electronic device of FIG. 1;

FIG. 5 is a schematic of a remote control representing an embodiment ofthe electronic device of FIG. 1;

FIG. 6 is a schematic of a game controller representing an embodiment ofthe electronic device of FIG. 1;

FIG. 7 is a schematic view of a device state, e.g., pointers, openapplications, and/or associated user data which may be stored on theelectronic device of FIG. 1;

FIGS. 8A-E are schematics of various configurations for carrying out asimplified data transfer between two embodiments of the electronicdevice of FIG. 1;

FIGS. 9A-F are schematics illustrating various configurations forcarrying out a “dual” simplified data transfer among three embodimentsof the electronic device of FIG. 1;

FIG. 10 is a block diagram of a simplified data transfer system fortransferring data between two embodiments of the electronic device ofFIG. 1;

FIG. 11 is a flowchart describing generally the operation of thesimplified data transfer system of FIG. 10;

FIGS. 12A-D are schematics illustrating user preferences which mayrelate to the simplified data transfer system of FIG. 10;

FIG. 13 is a schematic view of potential communication channels whichmay be employed by the simplified data transfer system of FIG. 10;

FIG. 14 is a schematic view of an embodiment in which initiation of thesimplified data transfer system of FIG. 10 takes place over near fieldcommunication (NFC);

FIG. 15 is a schematic view of the communication taking place during theinitiation of FIG. 14;

FIG. 16 is a flowchart describing an embodiment of a method forperforming the initiation of FIG. 14;

FIGS. 17A-C are schematics illustrating an alternative embodiment forperforming the initiation of the simplified data transfer system of FIG.10;

FIGS. 18A-B are schematics illustrating an alternative embodiment forperforming the initiation of the simplified data transfer system of FIG.10;

FIG. 19 is a flowchart describing an embodiment of a method forperforming the initiation of FIGS. 17-18;

FIG. 20 is a flowchart illustrating an embodiment of a method forinitiating network communication in the flowchart of FIG. 19;

FIG. 21 is a flowchart illustrating an embodiment of a method fordetermining which smart prompt to display following the initiation ofFIGS. 14-16;

FIGS. 22A-B are schematics of prompts that may issue in the method ofFIG. 21;

FIG. 23 is a flowchart describing another embodiment of a method fordetermining whether to display a smart prompt;

FIG. 24A-B are schematics of a context-based prompt that may bedisplayed based on determinations of the flowchart of FIG. 23;

FIG. 25 is a flowchart describing an embodiment of a method forperforming the data transfer of the simplified data transfer system ofFIG. 10;

FIGS. 26A and 26B are schematics of an exemplary response by a receivingdevice after receiving data in the simplified data transfer system ofFIG. 10;

FIG. 27 is a flowchart describing an embodiment of a method fordisplaying user data to be transferred in the simplified data transfersystem of FIG. 10;

FIG. 28 is a schematic view of another exemplary response by thereceiving device after receiving user data in the simplified datatransfer system of FIG. 10;

FIG. 29 is a flowchart describing an embodiment of an exemplary methodfor performing a simplified data transfer of FIG. 10;

FIG. 30 is a flowchart describing an embodiment of a method of using thesimplified data transfer system of FIG. 10;

FIGS. 31A-B are block diagrams illustrating delayed transfer simplifieddata transfer systems;

FIGS. 32A-B are flowcharts describing embodiments of methods for thedelayed transfer simplified data transfer systems of FIGS. 31A-B;

FIGS. 33A-C are block diagrams illustrating three-device simplified datatransfer system;

FIGS. 34A-C are flowcharts describing embodiments of methods forperforming the three-device simplified data transfer system of FIGS.33A-C;

FIGS. 35A-B are schematic views of a data drop prompt for transferringdata using the simplified data transfer systems of FIGS. 33A-C and34A-C;

FIG. 36 is a flowchart describing an embodiment of a method for usingthe simplified data transfer techniques of FIGS. 33A-C and 34A-C;

FIG. 37 is a block diagram illustrating a simplified data transferbetween a working device and a personal device via a remote storagelocation;

FIG. 38 is a flowchart describing an embodiment of a method forperforming the simplified data transfer of FIG. 37;

FIG. 39 is a flowchart describing an embodiment of a method forestablishing a direct connection between a working device and a personaldevice;

FIG. 40 is a block diagram illustrating a simplified data transferbetween a working device and a personal device;

FIG. 41 is a flowchart describing an embodiment of a method forperforming the simplified data transfer of FIG. 40;

FIG. 42 is a schematic of a screen that may be displayed on a workingdevice for the simplified data transfer of FIG. 37 or FIG. 40;

FIG. 43 is a schematic of another screen that may be displayed on aworking device for the simplified data transfer of FIG. 37 or FIG. 40;

FIGS. 44A-D are schematics of screens that may be displayed on apersonal device for the simplified data transfer of FIG. 37 or FIG. 40;

FIGS. 45A-C are schematics of other screens that may be displayed on apersonal device for the simplified data transfer of FIG. 37 or FIG. 40;

FIGS. 46A-B are schematics of other screens that may be displayed on apersonal device for the simplified data transfer of FIG. 37 or FIG. 40;

FIGS. 47A-E are schematics of other screens that may be displayed on apersonal device for the simplified data transfer of FIG. 37 or FIG. 40.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

Many people use more than one electronic device from day to day, buttransferring data from one device to another may be onerous. Forexample, a person may want to take an online map found on a homecomputer with them on their phone when they leave the house. Doing somay be complicated or daunting. The techniques described in thefollowing disclosure may allow a person to easily transfer data betweentwo or more devices. Using the techniques disclosed below, a person maytransfer an online map from their home computer to their phone by simplytapping the phone to the computer.

Turning first to FIG. 1, an electronic device 10 may be configured forsimplified data transfer. As discussed below with reference to FIGS.2-6, the electronic device 10 may represent, among other things, ahandheld device, a computer, a media player, a remote control, or a gamecontroller adapted to perform the simplified data transfer techniquesdescribed in greater detail below. As such, the electronic device 10 mayrepresent, for example, an iPhone® or iPod®, an iMac® or MacBook®, anAppleTV®, or an AppleTV® remote control available from Apple, Inc. orsimilar devices by any other manufacturer.

The electronic device 10 may be configured to perform the techniques forsimplified data transfer described in greater detail below and, as such,the electronic device 10 may be capable of storing and processing data,as described below with reference to FIG. 7. Embodiments of theelectronic device 10 may transfer the data in a simplified manner, asdescribed generally with reference to FIGS. 8-9. A more detaileddiscussion of the simplified data transfer techniques appears below withreference to FIGS. 10-37.

With reference to FIG. 1, the electronic device 10 may include at leastone central processing unit (CPU) 12. For example, the CPU 12 mayrepresent one or more microprocessors, and the microprocessors may be“general purpose” microprocessors, a combination of general and specialpurpose microprocessors, or ASICS. Additionally or alternatively, theCPU 12 may include one or more reduced instruction set (RISC)processors, video processors, or related chip sets. The CPU 12 mayprovide processing capability to execute an operating system, runvarious applications, and/or provide processing for one or more of thesimplified data transfer techniques described herein.

A main memory 14 may be communicably coupled to the CPU 12, which maystore data and executable code. The main memory 14 may representvolatile memory such as RAM, but may also include nonvolatile memory,such as read-only memory (ROM) or Flash memory. In buffering or cachingdata related to operations of the CPU 12, the main memory 14 may storeuser data associated with open applications running on the electronicdevice 10.

The electronic device 10 may also include nonvolatile storage 16. Thenonvolatile storage 16 may represent any suitable nonvolatile storagemedium, such as a hard disk drive or nonvolatile memory, such as Flashmemory. Being well-suited to long-term storage, the nonvolatile storage16 may store data files such as media (e.g., music and video files),software (e.g., for implementing functions on the electronic device 10),preference information (e.g., media playback preferences), lifestyleinformation (e.g., food preferences), exercise information (e.g.,information obtained by exercise monitoring equipment), transactioninformation (e.g., information such as credit card information),wireless connection information (e.g., information that may enable mediadevice to establish a wireless connection such as a telephoneconnection), subscription information (e.g., information that maintainsa record of podcasts or television shows or other media a usersubscribes to), as well as telephone information (e.g., telephonenumbers). It should be appreciated that user data associated with openapplications may be saved in the nonvolatile storage 16.

A display 18 may display images and data for the electronic device 10.It should be appreciated that only certain embodiments may include thedisplay 18. The display 18 may be any suitable display, such as liquidcrystal display (LCD), a light emitting diode (LED) based display, anorganic light emitting diode (OLED) based display, a cathode ray tube(CRT) display, or an analog or digital television. In some embodiments,the display 18 may function as a touch screen through which a user mayinteract with the electronic device 10.

The electronic device 10 may further include a user interface 20. Theuser interface 20 may represent indicator lights and user inputstructures, but may also include a graphical user interface (GUI) on thedisplay 18. In practice, the user interface 20 may operate via the CPU12, using memory from the main memory 14 and long-term storage in thenonvolatile storage 16. In an embodiment lacking the display 18,indicator lights, sound devices, buttons, and other various input/output(I/O) devices may allow a user to interface with the electronic device10. In a GUI embodiment, the user interface 20 may permit a user tointeract with interface elements on the display 18 by way of varioususer input structures, user input peripherals such as a keyboard ormouse, or a touch sensitive implementation of the display 18.

As should be appreciated, one or more applications may be open andaccessible to a user via the user interface 20 and displayed on thedisplay 18 of the electronic device 10. The applications may run on theCPU 12 in conjunction with the main memory 14, the nonvolatile storage16, the display 18, and the user interface 20. User data may beassociated with each open application. As will be discussed in greaterdetail below, instructions stored in the main memory 14, the nonvolatilestorage 16, or the CPU 12 of the electronic device 10 may permit asimplified transfer of pertinent user data associated with openapplications running the electronic device 10 to another electronicdevice 10. Rather than require a user to undertake a number ofcomplicated steps to transfer the user data from one electronic device10 to another electronic device 10, the user data may be automaticallytransferred with minimal user effort, as discussed below. As such, itshould be appreciated that the instructions for carrying out thesimplified data transfer of may represent a standalone application, afunction of the operating system, or a function of the hardware of theCPU 12, the main memory 14, or the nonvolatile storage 16.

In certain embodiments, the electronic device 10 may include locationsensing circuitry 22. The location sensing circuitry 22 may representseparate global positioning system (GPS) circuitry, but may alsorepresent algorithms, stored in the nonvolatile storage 16 or mainmemory 14 and carried out by the CPU 12, which may be used to inferlocation based on various observed factors. For example, the locationsensing circuitry 22 may represent an algorithm for approximatinggeographic location based on the detection of local 802.11x (Wi-Fi)networks or nearby cellular phone towers. As discussed below, theelectronic device 10 may employ the location sensing circuitry 22 as afactor for carrying out a smart data transfer. For example, the locationsensing circuitry 22 may assist the electronic device 10 in properlydetermining the most effective network for simplified data transfer.

With continued reference to FIG. 1, the electronic device 10 may alsoinclude a wired input/output (I/O) interface 24 for a wiredinterconnection between one electronic device 10 and another electronicdevice 10. The wired I/O interface 24 may represent, for example, auniversal serial bus (USB) port or an IEEE 1394 or FireWire® port, butmay also represent a proprietary connection. Additionally, the wired I/Ointerface 24 may permit a connection to user input peripheral devices,such as a keyboard or a mouse.

One or more network interfaces 26 may provide additional connectivityfor the electronic device 10. The network interfaces 26 may represent,for example, one or more network interface cards (NIC) or a networkcontroller. In certain embodiments, the network interface 26 may includea personal area network (PAN) interface 28. The PAN interface 28 mayprovide capabilities to network with, for example, a Bluetooth® network,an IEEE 802.15.4 (e.g., ZigBee) network, or an ultra wideband network(UWB). As should be appreciated, the networks accessed by the PANinterface 28 may, but do not necessarily, represent low power, lowbandwidth, or close range wireless connections. The PAN interface 28 maypermit one electronic device 10 to connect to another local electronicdevice 10 via an ad-hoc or peer-to-peer connection. However, theconnection may be disrupted if the separation between the two electronicdevices 10 exceeds the range of the PAN interface 28.

The network interface 26 may also include a local area network (LAN)interface 30. The LAN interface 30 may represent an interface to a wiredEthernet-based network, but may also represent an interface to awireless LAN, such as an IEEE 802.11x wireless network. The range of theLAN interface 30 may generally exceed the range available via the PANinterface 28. Additionally, in many cases, a connection between twoelectronic devices 10 via the LAN interface 30 may involve communicationthrough a network router or other intermediary device.

For some embodiments of the electronic device 10, the network interfaces26 may include the capability to connect directly to a wide area network(WAN) via a WAN interface 32. The WAN interface 32 may permit aconnection to a cellular data network, such as the Enhanced Data ratesfor GSM Evolution (EDGE) network or other 3G network. When connected viathe WAN interface 32, the electronic device 10 may remain connected tothe Internet and, in some embodiments, to another electronic device 10,despite changes in location that might otherwise disrupt connectivityvia the PAN interface 28 or the LAN interface 30. As will be discussedbelow, the wired I/O interface 24 and the network interfaces 26 mayrepresent high-bandwidth communication channels for transferring userdata using the simplified data transfer techniques discussed herein.

Certain embodiments of the electronic device 10 may also include a nearfield communication (NFC) interface 34. The NFC interface 34 may allowfor extremely close range communication at relatively low data rates(464 kb/s), and may comply with such standards as ISO 18092 or ISO21481, or it may allow for close range communication at relatively highdata rates (e.g., 560 Mbps), and may comply with the TransferJet®protocol. The NFC interface 34 may have a range of approximately 2 to 4cm. The close range communication with the NFC interface 34 may takeplace via magnetic field induction, allowing the NFC interface 34 tocommunicate with other NFC interfaces 34 or to retrieve information fromtags having radio frequency identification (RFID) circuitry. Asdiscussed below, the NFC interface 34 may provide a manner of initiatingor facilitating a simplified transfer of user data from one electronicdevice 10 to another electronic device 10.

FIGS. 2-6 illustrate various specific embodiments of the electronicdevice 10 of FIG. 1. It should be appreciated that the specificembodiments of the electronic device 10 depicted in FIGS. 2-6 arerepresentative only and should not be understood as exclusive. Turningfirst to FIG. 2, a handheld device 36 may represent an embodiment of theelectronic device 10 of FIG. 1. By way of example, the handheld device36 may be a portable phone or a portable media player, such as aniPhone® or an iPod® available from Apple Inc.

The handheld device 36 may have an enclosure 38 of plastic, metal,composite materials, or other suitable materials in any combination. Theenclosure 38 may protect the interior components of the handheld device36 from physical damage and electromagnetic interference (EMI).Additionally, the enclosure 38 may allow certain frequencies ofelectromagnetic radiation to pass through to wireless communicationcircuitry within the handheld device 36 to facilitate wirelesscommunication.

The display 18 of the handheld device 36 may include the user interface20 in the form of a GUI, which may have a number of individual iconsrepresenting applications that may be activated. In some embodiments ofthe handheld device 36, the display 18 may serve as a touch-sensitiveinput device and the icons may be selected by touch. In someembodiments, a simplified data transfer application icon 40 may beselectable by a user. Here, the simplified data transfer application isdesignated as “Grab & Go” to indicate to a user that selection of theicon 40 will allow the electronic device 10 to “grab” data from openapplications from another electronic device 10 so the user can “go” withthis data.

When the simplified data transfer application icon 40 is selected, thesimplified data transfer application may open. The simplified datatransfer application may facilitate data transfer using the simplifieddata transfer techniques described herein. The user interface 20 on thedisplay 18 of the handheld device 36 may also include status indicatoricons 42, which indicate the status of components of the handheld device36. For example, the status indicator icons may include a cellularreception meter, an icon to indicate when the PAN interface 28 isactive, or a battery life meter.

The handheld device 36 may connect to another electronic device 10, suchas by using the wired I/O interface 24 located at the bottom of thedevice. For example, the wired I/O interface 24 may be a proprietaryconnection for interconnecting the handheld device 36 and anotherelectronic device 10 via USB or FireWire®. Once connected, the devicesmay synchronize and/or transfer certain data. In particular, the wiredI/O interface 24 on the handheld device 36 may permit a communicationchannel to another electronic device 10 for simplified data transfer inaccordance with techniques discussed herein.

User input structures 44, 46, 48, and 50 may supplement or replace thetouch-sensitive input capability of the display 18 for interaction withthe user interface 20. By way of example, the user input structures 44,46, 48, and 50 may include buttons, switches, a control pad, keys,knobs, a scroll wheel, or any other suitable input structures. The userinput structures 44 and 46 may work in conjunction with the display 18to control functions of the device. Particularly, the user inputstructure 44 may be a lock/unlock sliding button to lock or unlock thehandheld device 36; the user input structure 46 may be a navigationbutton for navigating the user interface 20 to a default or home screen;the user input structures 48 may be a pair of buttons for navigating upor down a screen of the user interface 20 or for controlling volume; andthe user input structure 50 may be an on/off button.

Certain embodiments of the handheld device 36 may include telephonefunctionality. As such, the handheld device 36 may include audio inputstructures 52 and audio output structure 54. The audio input structures52 may be one or more microphones for receiving voice data from a user,and the audio output structure 54 may be a speaker for outputting audiodata, such as data received by the handheld device 36 over a cellularnetwork. In certain embodiments, an audio port 56 may facilitateperipheral audio input and output devices, such as headsets, speakers,or microphones, to be used with the handheld device 36.

As noted above, some embodiments of the electronic device 10 may includethe NFC interface 34. The handheld device 36 depicted in FIG. 2 mayinclude the NFC interface 34 in any suitable location within theenclosure 38. Because the NFC interface 34 may permit communication at avery short range, the location of the NFC interface 34 in the handhelddevice 36 may be indicated on the enclosure 38, as illustrated in FIG.2. The NFC interface 34 may enable the handheld device 36 to engage innear field communication (NFC) with other NFC enabled electronic devices10. For example, in the discussion below, the NFC interface 34 maypresent a manner of initiating a simplified data transfer between thehandheld device 36 and another electronic device 10.

Turning to FIG. 3, a computer 58 may represent another embodiment of theelectronic device 10 of FIG. 1. The computer 58 may be any computer,such as a desktop computer, a server, or a notebook computer, but mayalso be a standalone media player or gaming machine. By way of example,the computer 58 may be an iMac®, a MacBook®, or an AppleTV® by AppleInc. It should be noted that the computer 58 may also represent apersonal computer (PC) by another manufacturer. An enclosure 60 mayprotect internal components of the computer 58, including the NFCinterface 34. The NFC interface 34 may permit very close rangecommunication between the computer 58 and other NFC enabled electronicdevices 10, such as the handheld device 36.

The display 18 of the computer 58 may display the user interface 20 inthe form of a GUI. The user interface 20 of the computer 58 may depictany user data associated with applications running on the computer 58,generally referred to herein as the device state and indicated bynumeral 62. Additionally, the user interface 20 may include a variety oficons related to applications installed on the computer 58. One suchicon may be the simplified data transfer application icon 40. When thesimplified data transfer application icon 40 is selected, the simplifieddata transfer application may open. The simplified data transferapplication may facilitate data transfer using the simplified datatransfer techniques described herein.

A user of the computer 58 may interact with the user interface 20 withvarious peripheral input devices, such as a keyboard or mouse, which mayconnect to the computer 58 via the wired I/O interface 24. The wired I/Ointerface 24 may also provide a high bandwidth communication channel forinterconnecting other electronic devices 10, such as the handheld device36, to the computer 58. In certain embodiments, the computer 58 may alsoinclude the network interfaces 26.

FIG. 4 depicts a standalone media player 64 which represents anotherembodiment of the electronic device 10 of FIG. 1. The standalone mediaplayer 64 may be configured to operate with the simplified data transfertechniques described herein. By way of example, the standalone mediaplayer 64 may be an AppleTV® device by Apple, Inc. However, thestandalone media player 64 may also represent a media player by anothermanufacturer.

Within the enclosure 38 of the standalone media player 64 may residevarious components of the electronic device 10. For example, theenclosure 38 may house the nonvolatile storage 16 for storing mediafiles and media playback software and the CPU 12 for processing themedia files. Wireless network interfaces 26, such as the PAN interface28 and LAN interface 30, may also be located within the enclosure 38,allowing the standalone media player 64 to communicate with otherelectronic devices 10 or to connect to the Internet. Using the wirelessnetwork interfaces 26, the standalone media player 64 may obtain orexchange media content.

The standalone media player 64 may also include, among other things, anindicator light and infrared (IR) port 66 and audio/video (A/V) outputs68. The indicator light and IR port 66 may receive an IR control signalfrom a remote control and indicate to a user when the standalone mediaplayer 64 is on, off, receiving or exchanging content, or preparing fora simplified data transfer in accordance with techniques describedherein. The A/V outputs 68 may provide a manner for connecting thestandalone media player 64 to an analog or digital television or othermedia display devices. The standalone media player 64 may additionallyinclude the wired I/O interface 24, which may permit the standalonemedia player 64 to communicate rapidly with a wired connection toanother electronic device 10.

The standalone media player 64 may also include the NFC interface 34.With the NFC interface 34, the standalone media player 64 maycommunicate with another electronic device 10 having another NFCinterface 34. Using NFC communication via the NFC interface 34, thestandalone media player 64 and another electronic device 10 may initiatea simplified data transfer of media stored on the standalone mediaplayer 64, as described in greater detail below.

FIG. 5 illustrates a remote control 70, which may be used to control thestandalone media player 64 of FIG. 4 or the computer 58 of FIG. 3. Forexample, the remote control 70 may represent another embodiment of theelectronic device 10 of FIG. 1 and may be configured to operate with thesimplified data transfer techniques described herein. By way of example,the remote control 70 may be an AppleTV® remote control adapted toperform the simplified data transfer techniques described below. Itshould be understood, however, that the remote control 70 may representany remote control capable of performing the simplified data transfertechniques.

The enclosure 38 of the remote control 70 may protect the internalcomponents of the remote control 70 from physical damage or extraneouselectromagnetic radiation, while permitting control signals, such as IRcontrol signals, to exit for controlling the standalone media player 64or the computer 58. Internal components protected by the enclosure 38may include, for example, the CPU 12, the main memory 14, thenonvolatile storage 16, or the wireless network interfaces 26 of the PANinterface 28 or the LAN interface 30. The internal components may permitthe remote control 70 to store and transfer data in a simplified datatransfer, as discussed below.

The remote control 70 may include a multifunction button 72, which maypermit a user to play, pause, fast forward, or rewind media, increase ordecrease volume, or navigate a menu. Additionally, the remote control 70may include a menu button 74 for navigating the standalone media player64 or the computer 58 to a main menu screen. To control the standalonemedia player 64 or the computer 58, an infrared (IR) window 76 maypermit control signals to exit the enclosure 38 of the remote control70. The control signals which exit the IR window 76 may be received bythe indicator light and IR port 66 of the standalone media player 64 orby an IR peripheral device communicably coupled to the computer 58.

As indicated in FIG. 5, the remote control 70 may also include the NFCinterface 34. With the NFC interface 34, the remote control 70 maycommunicate with another electronic device 10 having another NFCinterface 34. Using NFC communication via the NFC interface 34, theremote control 70 and the other electronic device 10 may initiate asimplified data transfer to or from the remote control 70 according totechniques described in greater detail below.

FIG. 6 illustrates a game controller 78 for use with a video gamingsystem, the computer 58, or the standalone media player 64. The gamecontroller 78 may represent another embodiment of the electronic device10 of FIG. 1 configured to perform the simplified data transfertechniques described below. The game controller 78 may provide a mannerof interfacing with a game running on another electronic device 10. Theenclosure 38 of the game controller 78 may protect the internalcomponents of the remote control 70 from physical damage or extraneouselectromagnetic radiation. Internal components protected by theenclosure 38 may include, for example, the CPU 12, the main memory 14,the nonvolatile storage 16, or the wireless network interfaces 26 of thePAN interface 28 or the LAN interface 30. The internal components maypermit the game controller 78 to store and transfer user data (e.g.,game save data, digital photos, or music) using the simplified datatransfer techniques discussed below.

To interface with the video gaming system, the computer 58, or thestandalone media player 64, the game controller 78 may include variouscontrol buttons 80, such as a directional pad or other selectionbuttons. Indicator lights 82 may indicate to a user, among other things,when the game controller is on, off, or communicating with anotherelectronic device 10.

The game controller 78 may also include the NFC interface 34. With theNFC interface 34, the game controller 78 may communicate with anotherelectronic device 10 having another NFC interface 34. Using NFCcommunication via the NFC interface 34, the game controller 78 and theother electronic device 10 may initiate a simplified data transfer to orfrom the game controller 78 according to techniques described in greaterdetail below.

As described above, the electronic device 10 may take many forms andprovide many different functions, yet all are similar to the extent thatit may be useful to transfer the state of one electronic device 10and/or data on one electronic device 10 to another. FIG. 7 is aschematic view of an embodiment of a device state 62, which mayrepresent a device state, e.g., pointers, open applications, and/orassociated user data capable of running on the electronic device 10 ofFIG. 1. Using the simplified data transfer techniques discussed below,certain elements of the device state 62 may be transferred from oneelectronic device 10 to another electronic device 10 with minimal usereffort. The device state 62 may accordingly be present on the handhelddevice 36 of FIG. 2, the computer 58 of FIG. 3, the standalone mediaplayer 64 of FIG. 4, the remote controller 70 of FIG. 5, or the gamecontroller 78 of FIG. 6, to continue with the above examples.

By way of example, the device state 62 may include a web browser 84,such as Safari®; a spreadsheet application 86, such as Numbers '08®; apresentation application 88, such as Keynote '08®; a media managementapplication 90, such as iTunes®; a gaming platform 92; or a backupapplication 94 for storing and accessing recently modified or savedfiles, such as Time Machine®. The applications of the device state 62may run independently of or may form a part of the operating system ofthe electronic device 10. Moreover, though Safari®, Numbers '08®,Keynote '08®, iTunes®, and Time Machine® are products of Apple Inc., itshould be understood that the device state 62 may include applicationsby any manufacturer and designed for any platform.

It should be appreciated that the device state 62 may include more orfewer applications than depicted in FIG. 7. Particularly, the handhelddevice 36 may include a map application or an online video application.For example, the map application may display online maps and the onlinevideo application may play online video, rather than employ the webbrowser 84 for such tasks.

Each of the open applications 84, 86, 88, 90, 92, and 94 may have openfiles or other user data associated with each. For example, the webbrowser 84 may display a web page 96 or an online map 98. Thespreadsheet application 86 may run a spreadsheet 100. The presentationapplication 88 may run a presentation 102. The media managementapplication 90 may play a music file 104, such as a song, which may be apart of a playlist 106. Additionally or alternatively, the mediamanagement application may play a video file 108, such as a movie. Thegaming platform 92 may run a game 110. The backup application 94 maymaintain a number of recent files 112.

A user of the electronic device 10 may have any number of applicationsopen at a given time, and each application may have user data, such asone or more open files, associated therewith. The user may desire totransfer some or all of the user data of the device state 62 from theelectronic device 10 that the user is working on to another electronicdevice 10 in the user's possession. Rather than manually saving userdata associated with each application individually, then manuallytransferring the user data from the working electronic device 10 to thepersonal electronic device 10, the user may transfer the user data 96,98, 100, 102, 104, 106, 108, 110, and/or 112 of the device state 62 in asimplified manner according to techniques described below.

FIGS. 8A-E illustrate various configurations for carrying out asimplified data transfer 114 between two electronic devices 10. Itshould be appreciated that the configurations illustrated by FIGS. 8A-Eare representative only and are not exclusive, as the simplified datatransfer 114 may take place between any two electronic devices 10.

Turning first to FIG. 8A, the simplified data transfer 114 may takeplace between the computer 58 and the handheld device 36. By way ofexample, a user may be sitting at their desk at work with an importantspreadsheet open on their computer 58 when the user is called into anunexpected meeting. With no time to print the spreadsheet, the user mayuse the simplified data transfer system 114 to easily transfer a PDF ofthe spreadsheet onto their handheld device 36. Despite the short notice,the user may have the spreadsheet at their fingertips in the meetingusing the simplified data transfer system 114.

Turning next to FIG. 8B, the simplified data transfer 114 may also takeplace between two handheld devices 36A and 36B. For example, a user maywant to transfer an online map open on their handheld device 36A to thehandheld device 36B belonging to a friend. Using the simplified datatransfer 114, the user may easily transfer the online map by touchingthe devices together.

FIG. 8C similarly illustrates that the simplified data transfer 114 maytake place between two computers 58A and 58B. By way of example, a usermay be at work in front of their work computer 58A. The user maysuddenly realize that they needed a document open on their home computer58B. From the comfort of the office, the user may quickly and easilyretrieve the open document using the simplified data transfer 114.

As illustrated in FIG. 8D, the simplified data transfer 114 may alsooccur between the standalone media player 64 and the handheld device 36.For example, kids may be watching a movie on the standalone media player64 at home. It's time for a car trip, but the movie is not over. Usingthe simplified data transfer 114, parents may transfer the movie fromthe standalone media player 64 to the handheld device 36. The movie maybegin playing on the handheld device 36 where the standalone mediaplayer 64 left off, and the kids can finish the movie in the car.

Turning to FIG. 8E, the simplified data transfer 114 may also occurbetween the computer 58 and the standalone media player 64. By way ofexample, a user may be listening to a playlist of music on the computer58 in headphones while a roommate sleeps. When the roommate wakes up,the user may use the simplified data transfer 114 to transfer theplaylist to the standalone media player 64, picking up out loud wherethe headphones and computer 58 left off.

In many instances, users may desire to transfer data between two remoteelectronic devices 10. To further simplify the transfer, a thirdelectronic device 10 may serve as an intermediary. For example, FIGS.9A-F illustrate various configurations for carrying out a “dual”simplified data transfer 116 from a first electronic device 10 to athird electronic device 10, by way of a second electronic device 10. Itshould be appreciated that the configurations illustrated in FIGS. 9A-Fare representative only and are not exclusive. As indicated by FIGS.9A-F, the dual simplified data transfer 116 may involve two simplifieddata transfers 114.

Turning first to FIG. 9A, the dual simplified data transfer 116 may takeplace between two computers 58A and 58B via the handheld device 36. Byway of example, a user may want to bring home all the work documentsopen on a work computer 58A to a home computer 58B. The user maytransfer all the open work documents to the handheld device 36 by simplytapping it to the work computer 58A in the first simplified datatransfer 114. When the user arrives home, the user may tap the handhelddevice 36 to the home computer 58B in the second simplified datatransfer 114, transferring all the work documents from the work computer58A to the home computer 58B.

Turning next to FIG. 9B, the dual simplified data transfer 116 may alsotake place between the standalone media player 64 and the computer 58via the handheld device 36. For example, a user may be playing a movieon the standalone media player 64. If a roommate of the user wants to goto sleep, the user should finish the movie on the computer 58. The usermay first transfer the movie or a part of the movie onto the handhelddevice 36 using the first simplified data transfer 114. In the secondsimplified data transfer 114, the user may transfer the movie or part ofthe movie to the computer 58. As a result, the user may continue toenjoy the movie after the roommate has gone to bed.

FIG. 9C illustrates that the dual simplified data transfer 116 may alsotake place between the computer 58 and the standalone media player 64via the game controller 78. By way of example, a kid may be playing avideo game on the computer 58 using the game controller 78. If a parentneeds to use the computer 58, the kid may use the first simplified datatransfer 114 to save the game and store it on the game controller 78.Next, the kid may bring the game controller to the standalone mediaplayer 64. Using the second simplified data transfer, the kid maytransfer the game save data to the standalone media player 64, where thegame can be continued where the computer 58 left off.

Turning to FIG. 9D, the dual simplified data transfer 116 may also takeplace between two standalone media players 64A and 64B via the remotecontrol 70. For example, one family member may be watching a movie onthe standalone media player 64A on a small TV in a side room, while themain TV and the standalone media player 64B are occupied by otherswatching a TV show. When the others finish the TV show, themovie-watching family member may use the first simplified data transfer114 to transfer the movie or a pointer associated with the movie to theremote control 70. The movie-watcher may next go to the main TV with thestandalone media player 64B. Using the second simplified data transfer114, the movie-watching family member may transfer the movie or pointerassociated with the movie from the remote control 70 to the standalonemedia player 64B, and pick up the movie where it left off.

FIG. 9E illustrates that the dual simplified data transfer 116 may alsotake place between two standalone media players 64A and 64B via the gamecontroller 78. By way of example, a user may be playing a video game ata friend's house on the standalone media player 64A with the gamecontroller 78. When it is time to go home, the user may pick up the gamewhere it left off, using the dual simplified data transfer 116. First,the user may, for example, tap the game controller 78 to the standalonemedia player 64A to cause the first data transfer 114 and receiving gamesave data onto the game controller 78 from the standalone media player64A. When the user gets home, the user may, for example, tap the gamecontroller 78 to the standalone media player 64B to cause the seconddata transfer 114. With the game save data sent to the standalone mediaplayer 64B, the user may continue to play the game at home.

Turning to FIG. 9F, the dual simplified data transfer 116 may also takeplace between the standalone media player 64 and the computer 58 via theremote control 70. For example, a passenger in a car fitted with thestandalone media player 64 may be watching a TV show using the remotecontrol 70. When the car arrives home, the passenger may want to finishthe TV show on their computer 58. By tapping the remote control 70 tothe standalone media player 64, the user may initiate the firstsimplified data transfer 114, which may transfer the TV show or apointer associated with the TV show to the remote control 70. Next, theuser may tap the remote control 70 to the computer 58 at home, causingthe second simplified data transfer 114 to the computer 58. Thepassenger, now at home, may then finish the TV show where it left off inthe car.

FIG. 10 is a schematic view of a simplified data transfer system 118 fortransferring user data between two electronic devices 10. In thesimplified data transfer system 118, one of the electronic devices 10 istermed a working device 120, while the other is termed a personal device122. The working device 120 represents the one of the electronic devices10 which will be transferring its device state 62. The personal device122 represents the one of the electronic devices 10 which will bereceiving the device state 62 from the working device 120. The workingdevice 120 and the personal device 122 may be any variation of theelectronic device 10, as indicated by FIGS. 8A-E and 9A-F.

As illustrated in FIG. 10, the simplified data transfer system 118principally operates in three phases, an initiation 124, a smart prompt126, and a smart data transfer 128. Each phase may involve a number ofpossible steps which, as discussed below, may vary based on presetpreferences, available network communication channels between theworking device 120 and the personal device 122, or other factorsdescribing the context of the transaction. A general overview of theoperation of the simplified data transfer system 118 is described withreference to FIG. 11, preferences are described with reference to FIGS.12A-D, and available network communication channels are described withreference to FIG. 13.

With continued reference to FIG. 10, the simplified data transfer system118 may begin when either the working device 120 or the personal device122 causes the initiation 124, during which the working device 120 andthe personal device 122 may begin a simplified data transfer accordingto the techniques described herein. The initiation 124 may begin whenthe NFC interfaces 34 of the working device 120 and the personal device122 are placed in close proximity. Alternatively, the initiation 124 maybegin via a simplified data transfer application running on either thepersonal device 122 or the working device 120. The initiation 124 isdescribed in greater detail below with reference to FIGS. 14-20.

Following the initiation 124, the working device 120 or the personaldevice 122 may or may not display the smart prompt 126, depending onvarious factors describing the context of the data transfer transaction.For example, if factors indicate that both the working device 120 andthe personal device 122 are owned by different individuals or that thereis a large amount of data to be transferred, the smart prompt 126 mayappear on either the working device 120 or the personal device 122 toallow the selection of user data for transfer. Alternatively, if factorsindicate that both devices are owned by the same individual and only oneapplication is open on the working device 120, the smart prompt 126 maynot appear on either device and the smart data transfer 128 may beginautomatically. The smart prompt 126 is described in greater detail belowwith reference to FIGS. 21-24.

During the smart data transfer 128, the working device 120 may transferits device state 62 to the personal device 122. The working device 120and the personal device 122 may first determine a most appropriatecommunication channel based on the context of the transaction. Forexample, a preferred communication channel may be chosen based onfactors including shared communication capabilities, available networkpermissions, and physical proximity. The smart data transfer 128 isdescribed in greater detail below with reference to FIG. 25.

The working device 120 may subsequently transfer all or part of thedevice state 62 to the personal device 122 using the preferredcommunication channel. Upon receipt of the data, the personal device 122may prompt the user to open the data or may open certain dataautomatically. The receipt of user data following the smart datatransfer 128 is described in greater detail below with reference toFIGS. 26-28.

As should be appreciated, the simplified data transfer system 118 may beused for transferring data in a number of specific situations. Forexample, the working device 120 may be the computer 58 and the personaldevice 122 may be the handheld device 36. The above situation isdescribed in greater detail from the point of view of the working device120 and the personal device 122 with reference to FIG. 29, and from thepoint of view of a user with reference to FIG. 30.

The smart data transfer 128 of the simplified data transfer system 118may additionally or alternatively take place in two stages. A firsttransfer may transfer the user data of the device state 62 to remotestorage or into the main memory 14 or the nonvolatile storage 16 of theworking device 120. In a second transfer at a later time, the user dataof the device state 62 may be transferred from storage to the personaldevice 122. The situation when the smart data transfer 128 involves twostages is described in greater detail below with reference to FIGS.31-32.

Finally, the smart data transfer 128 of the simplified data transfersystem 118 may additionally or alternatively be used twice among threeelectronic devices 10, as depicted in FIGS. 9A-F. As such, thesimplified data transfer system 118 may be used to transfer user data orpointers associated with the user data from the first device to thesecond device. The simplified data transfer system 118 may next be usedto transfer the user data from the second device to the third device.Employment of the simplified data transfer system 118 for transferringdata among three devices is described in greater detail below withreference to FIGS. 33-35.

As should further be appreciated, the use of the simplified datatransfer system 118 for transferring data among three devices may occurin a variety of specific situations. For example, the working device 120may be the computer 58 having the presentation 102 open and the personaldevice 122 may be the handheld device 36. A user may employ thesimplified data transfer system 118 to transfer the presentation 102from the working device 120 to another computer 58 by way of thepersonal device 122. The above situation is described in greater detailfrom the point of view of the working device 120 and the personal device122 with reference to FIG. 36, and from the point of view of a user withreference to FIG. 37.

Turning to FIG. 11, a flowchart 130 illustrates generally the operationof the simplified data transfer system 118. The flow chart 130 describesthe general steps associated with each phase of the simplified datatransfer system 118. Particularly, steps 132 through 138 represent stepsfor the initiation 124, steps 140 and 142 represent steps associatedwith the smart prompt 126, and steps 144 through 148 represent stepsassociated with the smart data transfer 128.

Step 132 represents a first step to the initiation 124 of the simplifieddata transfer system 118. In step 132, communication between the workingdevice 120 and the personal device 122 may first be initiated in avariety of ways. As discussed below with reference to FIGS. 14, 17, and18, communication between the working device 120 and the personal device122 may begin when the NFC interfaces 34 of the working device 120 andthe personal device 122 are placed in close proximity or, alternatively,when a simplified data transfer application running on either thepersonal device 122 or the working device 120 initiates communicationwith the other.

In step 134, the working device 120 and the personal device 122 maycommunicate information describing the capabilities of each device tothe other. The information communicated in step 134 may be used in latersteps to determine, for example, which prompt to issue for the smartprompt 126 or which network connection to establish for the smart datatransfer 128. In the next step 136, the working device 120 may determinewhich user data of the device state 62 may be prepared for transfer.During step 136, the user data associated with various open applicationsof the device state 62 may be saved and stored in a separate location inthe main memory 14 or the nonvolatile storage 16 of the working device120. In step 138, the working device 120 may communicate a basicdescription of the user data of the device state 62 which is to betransferred to the personal device 122.

Steps 140 and 142 represent steps associated with the smart prompt 126.In step 140, the working device 120 or the personal device 122 mayconsider a variety of factors to determine whether and which kind ofsmart prompt to issue. For example, the working device 120 or thepersonal device 122 may consider stored preferences, the data expectedto be transferred, the method used to begin the initiation 124, or otherfactors, such as physical proximity of the personal device 122 to theworking device 120 (i.e., the location determined by the locationsensing circuitry 22). In step 142, the working device 120 or thepersonal device 122 may or may not issue a prompt based on theconsiderations undertaken in step 140.

Steps 144 through 148 represent steps associated with the smart datatransfer 128. In step 144, the working device 120 or the personal device122 may consider a variety of factors in preparation for determiningwhich communication channels may be used for the smart data transfer128. For example, the working device 120 or the personal device 122 mayconsider stored preferences, the data expected to be transferred, themethod used to begin the initiation 124, or other factors, such asphysical proximity of the personal device 122 to the working device 120(i.e., the location determined by the location sensing circuitry 22).

Based on the considerations taken in step 144, the working device 120 orthe personal device 122 may select a network communication channel forthe transfer to take place. Having chosen the network communicationchannel over which to transfer the user data from the device state 62 ofthe working device 120 to the personal device 122, in step 148, the datamay be transferred. It should be noted that, based on the deviceinformation exchanged by the working device 120 and the personal device122 in step 136, the working device 120 may convert certain user dataprior to transfer. For example, if the personal device 122 lacks thecapability to process a particular type of document, the working device120 may first convert the document to an image or PDF which the personaldevice 122 may display prior to transfer.

FIGS. 12A-D illustrate various preferences which may be set insimplified data transfer software which may run on electronic devices10. The preferences may serve as factors for determining, for example,which data is to be saved for transfer during the initiation 124,whether and of which type of prompt to issue for the smart prompt 126,and which network to select for performing the smart data transfer 128.

Turning first to FIG. 12A, a preference overview page 150 may include avariety of preference category buttons 152 through 156 and a save button158. The preference category button 152 may allow configuration ofpreferences associated with particular devices that a user may possess;the preference category button 154 may allow configuration ofpreferences associated with particular networks, such as thoseillustrated in FIG. 13; and the preference category button 156 may allowconfiguration of preferences associated with certain file types or filesizes. The save button 158 may allow preference configurations to besaved in the main memory 14 or the nonvolatile storage 16 of theelectronic device 10.

FIG. 12B illustrates device preferences 152 which may appear uponselection of the preference category button 152. The device preferences152 may include any number of preferences associated with particulardevices. For example, the device preferences 152 may include which typeor size of user data associated with the device state 62 of eachparticular device to transfer; which preferred network connection tomake to each particular device; whether to trust by default certainother unknown electronic devices 10; or which versions of files torequest from each particular device when multiple versions exist on thesame device, etc.

With continued reference to FIG. 12B, device preferences 152 regardingthe type or size of user data associated with the device state 62 ofeach particular device may allow unique selections based on the workingdevice 120. The unique preferences for selections for each workingdevice 120 that a given personal device 122 may establish a simplifieddata transfer 114 or 116 may include, for example, whether to transferall open files; whether to transfer certain specific file types; whetherto transfer files above or beneath a certain size; whether to transferuser data associated only with the topmost open application or user dataassociated with certain applications or types of applications (e.g.,only productivity or business applications, entertainment applications,family applications, gaming applications, media applications,educational applications, accounting applications, etc.); whether toprioritize the transfer of user data associated with the topmost openapplication or user data associated with certain applications or typesof applications; whether to transfer files having certain ratings, suchas MPAA ratings, above or below a predetermined threshold; whether totransfer user data having certain keywords; whether to transfer userdata which may be capable of being processed by the receiving personaldevice 122; or whether to transfer user data generated by a differentuser or only to transfer user data generated by the same user. It shouldbe appreciated that the preferences described above may not only specifywhich types of user data may be transferred, but also which user data isdisplayed as transferable to the personal device 122.

To use the example introduced with reference to FIG. 8A above, a usermay be sitting at their desk at work with an important spreadsheet openon their computer 58 when the user is called into an unexpected meeting.The user may have a number of other personal applications running. Thepreferences described above may allow the user to “grab” only filesrelated to work from the user's work computer, such as only user dataassociated with productivity applications. In this way, the user maytransfer only the important spreadsheet in the simplified data transfer114, showing up to the meeting with only those files pertinent to work.

Similarly, a user may be working on their personal finances whilelistening to music using their computer at home. As it's time for theuser to go in to work, the user may want to continue listening to themusic on the train on the way. The preferences described above may allowthe user to avoid “grabbing” files related to personal finance orcertain keywords from the user's home computer. When the user transfersthe media in the simplified data transfer 114, the user's personalfinances may remain privately on the computer at home.

Preferred connections for use with each device may include, for example,whether to connect using the fastest available connection; whether toconnect using only the Internet or not ever using the Internet; whetherto connect using certain specified encryption schemes or to require apasscode or passkey before transfer may occur; whether to requireproximity based on the physical location of the electronic devices 10(i.e., as determined by the location sensing circuitry 22); or whetherto prefer a particular, specified connection to the particular device.

Preferences regarding whether to trust by default certain other unknownelectronic devices 10 may represent preferences which may be preset by,among others, developers, third party retailers, or wireless carriers.By presetting certain other unknown devices to be trustworthy among thedevice preferences 152, the developers, third party retailers, orwireless carriers may allow trust by default for certain devices whichmay be manufactured, sold, or employed by the same.

With regard to preferences associated with which versions of files torequest from each particular device when multiple versions exist on thesame device, the preferences may include whether to transfer all suchfiles; whether to transfer only the most recently modified files; orwhether to transfer only those files most recently modified by a certainuser.

FIG. 12C illustrates network preferences 154 which may appear uponselection of the preference category button 154. The network preferencesmay relate specifically to each type of network connection which may beavailable for the smart data transfer 128 and may include, for example,preferences reflecting a generally preferred network order or generallypreferred security measures.

Preferences reflecting a generally preferred network order may include,for example, whether to set a particular network connection aspreferred; whether to set the network connection as not to be used;whether to set the network connection to be used only in certaininstances, such as within a certain proximity based on the physicallocation of the electronic devices 10 (i.e., as determined by thelocation sensing circuitry 22), when both electronic devices 10 sharethe same user, or when the initiation 124 of the simplified datatransfer system 118 is begun in a certain manner (e.g., by NFC or inresponse to a prompt in simplified data transfer software); whether toavoid a particular network if the use of the network may requireadditional cost; or whether to order various network connections bysetting a level of priority.

Generally preferred security measures may include, for example, whetherto restrict connecting via a particular network to certain trustedconnections; whether to use certain types of encryption, such as WPAencryption; whether to require passcodes or passkeys; or whether torequire the use of QR encryption.

FIG. 12D illustrates file type/size preferences 156, which may appearupon selection of the preference category button 156. The file type/sizepreferences 156 may include, for example, which file types may receivepriority in transfer; which file types to transfer or not to transfer;or which file sizes to transfer or not to transfer.

Preferences regarding which files may receive priority in transfer mayinclude, for example, establishing priority based on whether a file isassociated with a productivity or office-related software product;whether a file represents user data created or modified by a particularuser, such as the owner of the receiving device; whether a file iswithin or in excess of a particular size; which network communicationchannels may be available for the smart data transfer 128; whether afile is capable of being processed natively by the receiving device;whether a file is of a particular type; or whether a file is to betransferred from a particular device or a particular class of devices.

Preferences associated with which file types to transfer or not totransfer may include, for example, preferences limiting transfer only tocertain specified files; limiting transfer to only files capable ofbeing processed by the receiving device; not limiting files at all; orrequiring a conversion of files not capable of being natively processedto an appropriate form (e.g., requiring conversion of a document into animage file or PDF).

With regard to preferences associated with which file sizes to transferor not to transfer, such preferences may include, for example, whetherto transfer files above a particular size; which network to prioritizebased on file size; or whether to transfer only a portion of a fileabove a particular size.

Reviewing FIGS. 12A-D, it should be understood that a user may adjustthe various preferences manually, or the preferences may be adjustedautomatically based on user behavior. By way of example, a user may useone electronic device 10, such as the handheld device 36, to obtain viathe simplified data transfer system 118 user data associated with thedevice state 62 of another electronic device 10, such as the computer58. If the user cancels the transfer of all of a particular type of userdata while the data is being transferred, the preferences may be alteredto reflect the user behavior. For example, the preferences may be set tolower the priority of transfer of the particular type of file, may beset to prevent the file type from being transferred, or may set the filetype to be one which is not transferred over certain premium networkswhich may levy additional charges.

It should also be appreciated that the preferences of FIGS. 12A-D maypermit developers, third party retailers, or wireless carriers topreinstall preferences in addition to or in lieu of those customizablepreferences chosen by users. For example, a developer or third partyretailer may preinstall preferences regarding certain other electronicdevices 10, such as those produced by the developer or sold by the thirdparty retailer. A wireless carrier may preinstall a preference regardingcertain wireless data networks which may be accessed by the WANinterface 132, such as the EDGE network or other 3G networks.

FIG. 13 is a schematic view of potential communication channels 160between the working device 120 and the personal device 122, whichrepresent the electronic devices 10 configured for transfer in thesimplified data transfer system 118. Each communication channel 160shared between the working device 120 and the personal device 122 may beused for the initiation 124 or the smart data transfer 128. Whichcommunication channel is used for the initiation 124 or the smart datatransfer 128 may depend on a variety of factors, including, for example,the preferences discussed with reference to FIGS. 12A-D above or thecontext of the initiation 124 discussed with reference to FIGS. 14-20.

Reviewing each of the communication channels 160 in turn, if each of theworking device 120 and the personal device 122 include NFC interfaces34, a near field communication (NFC) communication channel 162 maycommunicably link the two devices. When the NFC interfaces 34 of theworking device 120 and the personal device 122 are placed in closeproximity, the working device 120 and the personal device 122 mayestablish the NFC communication channel 162.

It should be appreciated that the NFC communication channel 162 maygenerally remain open for a relatively short period of time and mayoperate at a lower bandwidth. As such, the NFC communication channel 162may generally accommodate the initiation 124, while the subsequent smartdata transfer 128 may generally take place via another of thecommunication channels 160 described below.

As noted above, the working device 120 and the personal device 122 maypotentially be connected through many of the communication channels 160other than the NFC channel 162. Particularly, if either device lacks theNFC interface 34, the initiation 124 instead may take place over theother of the communication channels 160. If the initiation 124 takesplace over the other of the communication channels 160, the initiation124 may begin when a user initiates a transfer using a smart datatransfer application on either the working device 120 or the personaldevice 122, as described with reference to FIGS. 17-18. In someembodiments, although the working device 120 and the personal device 122may both include the NFC interface 34, a user may elect to have theinitiation 124 take place over another one of the communication channels160.

Among the possible communication channels 160 other than the NFC channel162 is a personal area network (PAN) communication channel 164,connected through the PAN interfaces 28 of each device. By way ofexample, the PAN communication channel 164 may represent a peer-to-peerBluetooth® connection, an IEEE 802.15.4 (e.g., ZigBee) network, or anultra wideband network (UWB) between the working device 120 and thepersonal device 122.

The working device 120 and the personal device 122 may additionally oralternatively be connected via a local area network (LAN) communicationchannel 166. The respective LAN interfaces 30 of the working device 120and the personal device 122 may share a peer-to-peer connection directlyto one another via the LAN communication channel 166, or may connect toone another via a router or a network controller along the LANcommunication channel 166. The LAN communication channel 166 mayrepresent a wired connection, such as an Ethernet connection, but mayalso represent a wireless connection, such as an IEEE standard 802.11.xwireless network, or Wi-Fi.

It should be appreciated that the working device 120 and the personaldevice 122 may establish the PAN communication channel 164 or the LANcommunication channel 166 using a device identification networkingprotocol. By way of example, the device identification networkingprotocol may be Bonjour® by Apple Inc. Each of the working device 120and the personal device 122 may broadcast using internet protocol (IP)their identifications and services, programs, and/or communicationcapabilities that each device may have. The working device 120 or thepersonal device 122 may receive information via the deviceidentification networking protocol so as to open peer-to-peerconnections via the PAN communication channel 164 or the LANcommunication channel 166. As should be appreciated, more than oneelectronic device 10 may be broadcasting information using the deviceidentification networking protocol. As such, the personal device 122 mayselect based on preferences with which electronic device 10 to initiatethe simplified data transfer 114.

While the working device 120 or the personal device 122 may be connectedvia the PAN communication channel 164 or the LAN communication channel166, the devices may also be connected by way of the Internet 168. Byconnecting to one another via the Internet 168, the working device 120and the personal device 122 may remain physically remote from oneanother while the simplified data transfer 114 occurs. Connecting viathe Internet 168 may also allow the working device 120 and the personaldevice 122 to retain communicative capabilities if a local peer-to-peerconnection, such as communication channels 164 or 166, is disrupted orlost.

To locate one another over the Internet 168, the working device 120 orthe personal device 122 may first query a web service 170 to obtain aninternet protocol (IP) address of the other. The web service 170 mayrepresent a dynamic domain name system (DNS) service, which may maintainthe current IP address of each device by communicating with a pluginassociated with the simplified data transfer application residing oneach device. By way of example, the web service 170 may be a function ofthe Back to My Mac® service from Apple, Inc.

The web service 170 may also provide remote storage capability tofacilitate the smart data transfer 128. As discussed further below withreference to FIGS. 31-34, the smart data transfer 128 may involve atemporary transfer of user data of the device state 162 of the workingdevice to remote storage associated with the web service 170. From theremote storage associated with the web service 170, the user data maythereafter be transferred to the personal device via the Internet 168 orvia a direct connection to the web service 170.

With further reference to FIG. 13, the working device 120 may reach theInternet 168 via its LAN interface 30 or via a wide-area network (WAN)communication channel 172, which may represent, for example, a cellulardata network such as EDGE or a 3G network. Similarly, the personaldevice 122 may connect to the Internet 168 via its LAN interface 30 orits WAN interface 32. If the personal device 122 connects to theInternet via the WAN interface 32, it may do so via a wide area network(WAN) communication channel 174, which may also represent, for example,a cellular data network such as EDGE or a 3G network.

It should be appreciated that the working device 120 and the personaldevice 122 may also establish a connection directly to the web service168 directly via the respective WAN interfaces 32 of the devices. Theworking device 120 may connect to the web service 170 via a wide areanetwork (WAN) communication channel 176, which may represent, forexample, a cellular data network such as EDGE or a 3G network.Similarly, the personal device 122 may connect to the web service 170via a wide area network (WAN) communication channel 178, which may alsorepresent, for example, a cellular data network such as EDGE or a 3Gnetwork.

The working device 120 and the personal device 122 may also be connectedto one another via a wired input/output (I/O) communication channel 180.The wired I/O communication channel 180 may generally permit anexceptionally rapid transfer of data between the working device 120 andthe personal device 122. As discussed below, any of the potentialcommunication channels 160 may provide a manner of communicating duringthe initiation 124 or during the smart data transfer 128, and one of thecommunication channels 160 employed for the initiation 124 may vary fromthat employed by the smart data transfer 128.

FIG. 14 illustrates an embodiment in which the initiation 124 of thesimplified data transfer system 118 takes place over the NFCcommunication channel 162 between the working device 120 and thepersonal device 122. It should be noted that although FIG. 14 depictsthe working device 120 as the computer 58 and the personal device 122 asthe handheld device 36, the working device 120 and the personal device122 may represent any embodiment of the electronic devices 10 having theNFC interface 34.

As indicated by FIG. 14, communication involved in the initiation 124may take place over the NFC communication channel 162 between theworking device 120 and the personal device 122. To open the NFCcommunication channel 162, a user may tap the NFC interface 34 of thepersonal device 122 to within a predetermined distance (e.g.,approximately 2 cm) of the NFC interface 34 of the working device 122.With the NFC communication channel 162 open, the working device 120 andthe personal device 122 may communicate information to one another overthe NFC communication channel 162 in preparation for the smart prompt126 and the smart data transfer 128. Such information exchanged duringthe initiation 124 may include, for example, capabilities associatedwith each device, certain user preferences, available networkconfiguration data, or pointers or low bandwidth elements relating touser data associated with the device state 62 of the working device 120.The information communicated over the NFC communication channel 162 maygenerally include short messages in extensible markup language (XML) orany other form. The messages exchanged over the NFC communicationchannel 162 during the initiation 124 are discussed further below.

FIG. 15 is a schematic view of an embodiment of the initiation 124taking place over the NFC communication channel 162. The embodimentillustrated in FIG. 15 may arise when the NFC interfaces 34 of theworking device 120 and the personal device 122 are placed in closeproximity, as illustrated in FIG. 14 and described above.

The NFC communication carried out the initiation 124 may take placebetween the working device 120 and the personal device 122. Although theworking device 120 is illustrated as the computer 58 and the personaldevice 122 is illustrated as the handheld device 36, the working device120 and the personal device 122 may represent any embodiments of theelectronic devices 10 having the NFC interface 34.

Prior to the start of the initiation 124, the personal device 122 may bein a “wake on NFC” mode, as indicated by block 182. In the “wake on NFC”mode, the NFC interface 34 of the personal device 122 may remaininactive until the NFC interface 34 receives an NFC signal from anotherNFC interface 34. At the same time, as indicated by block 184, the NFCinterface 34 of the working device 120 may be in a host mode. Being inthe host mode, the NFC interface 34 of the working device 120 mayperiodically emit NFC signals to seek out other proximate NFC interfaces34.

The initiation 124 over may begin with an initiation handshake 186. Theinitiation handshake 186 may start when a user taps the NFC interface 34of the personal device to the NFC interface 34 of the working device120, as indicated by block 188. As the NFC interface 34 of the workingdevice 120 may be in a host mode, the NFC interface 34 of the workingdevice 120 may periodically emit a ping message 190. The NFC interface34 of the personal device 122 may receive the ping message 190, causingthe NFC interface 34 of the personal device 122 to awake, as indicatedby block 192. Subsequently, the NFC interface 34 of the personal device122 may reply with an acknowledgement (ACK) message 194, which may bereceived by the NFC interface 34 of the working device 120.

Following the initiation handshake 186, the working device 120 and thepersonal device 122 may exchange device profiles 196. The deviceprofiles 196 may include a variety of information regarding thecapabilities of the working device 120 and the personal device 122. Forexample, the device profiles 196 may include messages of any form,including extensible markup language (XML), which may denote the devicename, serial number, owner name, type of device, as well as otheridentifying information. The other identifying information may include,for example, a service user name. The device profiles 196 mayadditionally denote capabilities of the personal device 122 or theworking device 120 by indicating which applications, drivers, orservices may be installed on each device.

As indicated by blocks 198 and 200, the personal device 122 and theworking device 120 may next authenticate one another, based at least inpart on the device profiles 196 previously exchanged. In the deviceauthentication of blocks 198 and 200, the personal device 122 or theworking device 120 may determine whether the other is trusted using anynumber of authentication schemes. The initiation 124 may be cancelled ifeither the personal device 122 or the working device 120 fails toauthenticate the other.

For example, the personal device 122 and the working device 120 may relyon a private key known to both devices, which may have been exchangedprior to the initiation 124. Alternatively, the personal device 122 andthe working device 120 may rely on a combination of a public key and aprivate key. Under such a scheme, the personal device 122 and theworking device 120 may each exchange public keys associated with oneanother prior to or during the device authentication of blocks 198 and200, or may obtain public keys from another source, such as the webservice 170. The personal device 122 and the working device 120 mayverify the public keys with a certificate authority over the Internet168 or via a web of trust. In some embodiments, the web service 170 mayrepresent the certificate authority. If there is any link broken in thechain of trust, the initiation 124 may be terminated.

Following the device authentication of blocks 198 and 200, the personaldevice 122 and the working device 120 may scan for available networkcommunication channels 160, as noted by blocks 202 and 204. Afterscanning for the available network communication channels 160, thepersonal device 122 and the working device 120 may exchange networkconfiguration information 206. The network configuration information 206may include, for example, XML messages denoting lists of networkcommunication channels 160 accessible via the working device 120 or thepersonal device 122. Among other things, the network configurationinformation 206 may include known authorization keys and service setidentifier (SSID). By way of example, the network configurationinformation 206 may include PAN interface 28 configuration information,such as a Bluetooth serial number, MAC address, and an associatedpassword, as well as LAN interface 30 configuration information, such asa WiFi IP address, a WiFi MAC address, and a WiFi SSID. The networkconfiguration information 206 may be stored for use at a later time topermit the personal device 122 and the working device 120 to ascertain ahigher bandwidth connection.

The personal device 122 and the working device 120 may remain incommunication via the NFC communication channel 162 to transferadditional information. As illustrated in FIG. 15, the working device120 may transmit device state pointers 208 to the personal device 122,which may describe the user data of the working device 62 which is to betransferred. The device state pointers 208 may represent a message, suchas an XML message, that includes the filename, associated application,file size, or other related information associated with each file thatmay be transferred. For example, the other related information mayinclude whether or not a file has been read, a geographic location wherethe file was created or modified using a convention such as GeoRSS, arelated uniform resource locator (URL), the hierarchy of the applicationwith which the file is associated, the location of the application onthe screen of the working device 120 with which the file is associated,the last device which modified the file, etc. The working device 120 mayalso transfer certain low bandwidth elements 210 associated with theuser data of the device state 62 of the working device 120. Such lowbandwidth elements 210 may include, for example, thumbnail images ofeach file to be transferred or excerpts of data from each file.

Though the device state pointers 208 and the low bandwidth elements 210may be transferred via the NFC communication channel 162, as indicated,other communication channels 160 may additionally or alternatively beemployed to do so. For example, the device state pointers 208 or the lowbandwidth elements may be transferred over the PAN communication channel164 or the LAN communication channel 166.

FIG. 16 is a flowchart 212 describing an embodiment of a method forperforming the initiation 124 via the NFC communication channel 162, asillustrated by FIGS. 14-15. In a first step 214, the personal device 122and the working device 120 may begin the initiation 124 by way of theinitiation handshake 186. As illustrated in FIG. 15 and described above,the initiation handshake 186 may occur when the NFC interfaces 34 of thepersonal device 122 and the working device 120 are placed in closeproximity to one another. The working device 120 may subsequently emit aping 190 to wake the NFC interface 34 of the personal device 122, andthe personal device 122 may reply with an ACK 194 to the working device120.

In step 216, the personal device 122 and the working device 120 mayexchange device profiles 196. As noted above with reference to FIG. 15,the device profiles 196 may include a variety of data describing thecapabilities of the personal device 122 and working device 120. Forexample, the device profiles 196 may include messages of any form,including extensible markup language (XML), which may denote the devicename, serial number, owner name, type of device, as well as otheridentifying information. The other identifying information may include,for example, a service user name. The device profiles 196 mayadditionally denote capabilities of the personal device 122 or theworking device 120 by indicating which applications, drivers, orservices may be installed on each device.

In step 218, the personal device 122 and the working device 120 may eachperform a device authentication process based at least in part on thedevice profiles 196 previously exchanged. During the deviceauthentication, the personal device 122 or the working device 120 maydetermine whether the other is trusted. As described above, the personaldevice 122 and the working device 120 may rely on a private key known toboth devices, or a combination of a public and a private key. Theinitiation 124 may be cancelled if either the personal device 122 or theworking device 120 fails to authenticate the other.

In a next step 220, the personal device 122 and the working device 120may scan for available network communication channels 160, over whichdata may be transferred at a later time. In step 222, after scanning forthe available network communication channels 160, the personal device122 and the working device 120 may exchange network configurationinformation 206. As discussed above with reference to FIG. 15, thenetwork configuration information 206 may include, for example, XMLmessages denoting lists of network communication channels 160 accessiblevia the working device 120 or the personal device 122. Among otherthings, the network configuration information 206 may include knownauthorization keys and service set identifier (SSID). By way of example,the network configuration information 206 may include PAN interface 28configuration information, such as a Bluetooth serial number, MACaddress, and an associated password, as well as LAN interface 30configuration information, such as a WiFi IP address, a WiFi MACaddress, and a WiFi SSID. The network configuration information 206 maybe stored for use at a later time to permit the personal device 122 andthe working device 120 to ascertain a higher bandwidth connection.

In steps 224 and 226, the personal device 122 and the working device 120may remain in communication via the NFC communication channel 162 totransfer additional information. In step 224, the working device 120 maytransmit device state pointers 208 to the personal device 122, which maydescribe the user data of the working device 62 which is to betransferred. The device state pointers 208 may represent a message, suchas an XML message, that includes the filename, associated application,file size, or other related information associated with each file thatmay be transferred. For example, the other related information mayinclude whether or not a file has been read, a geographic location wherethe file was created or modified using a convention such as GeoRSS, arelated uniform resource locator (URL), the hierarchy of the applicationwith which the file is associated, the location of the application onthe screen of the working device 120 with which the file is associated,the last device which modified the file, etc.

In step 226, the working device 120 may transfer certain low bandwidthelements 210 associated with the user data of the device state 62 of theworking device 120. Such low bandwidth elements 210 may include, forexample, thumbnail images of each file to be transferred or excerpts ofdata from each file.

Though the device state pointers 208 and the low bandwidth elements 210may be transferred via the NFC communication channel 162 in steps 224and 226, other communication channels 160 may additionally oralternatively be employed to do so. For example, in steps 224 or 226,the device state pointers 208 or the low bandwidth elements may betransferred over the PAN communication channel 164 or the LANcommunication channel 166.

FIGS. 17A-C and 18A-B illustrate alternative manners of performing theinitiation 124. With reference first to FIGS. 17A-C, one manner ofperforming the initiation 124 may begin when a user selects thesimplified transfer application icon 50 on the personal device 122,which may be the handheld device 36. Upon selection of the icon 50, adevice selection screen 228 may appear, as indicated by FIG. 17B. Withthe device selection screen 228, a user may select a working device 120with which to begin a data transfer from among working device selectionbuttons 230. As should be appreciated, the working devices 120 appearingamong the working device selection buttons 230 represent devices sharingone of the possible communication channels 160 of FIG. 13.

Turning to FIG. 17C, a data transfer screen 232 may appear after theuser selects from among the working devices 120 from the working deviceselection buttons 230 depicted in FIG. 17B. Alternatively, the datatransfer screen 232 may appear immediately upon selection of thesimplified data transfer application icon 50. As indicated in FIG. 17C,prior to the initiation 124, the screen may be yet unpopulated. Thescreen may also provide an indication such as “No Items: press here tograb.” When a user selects a refresh button 233 or presses on the blankareas of the data transfer screen 232, the personal device 122 mayinvoke a transfer event in the simplified data transfer application.Subsequently, the initiation 124 may begin as described below withreference to FIG. 19.

It should be appreciated that a user may decide with which workingdevice 120 to establish the simplified data transfer 114 from the datatransfer screen 232. A button such as the button labeled “Source” mayallow a user to select the working device 120 from the data transferscreen 232. As noted above with reference to FIG. 13, the possibleworking devices 120 may be visible to the personal device 122 over oneof the network communication channels 160, which may be identified andestablished using a protocol such as Bonjour® from Apple Inc.

FIGS. 18A-B illustrate a similar manner of performing the initiation124, which may begin when a user selects the simplified data transferapplication icon 50 on the working device 120, which may be the computer58. Upon selection of the icon 50, a device selection screen 234 mayappear, as indicated by FIG. 18B. With the device selection screen 234,a user may select a personal device 122 with which to begin a datatransfer from among personal device selection buttons 236. As should beappreciated, the personal devices 120 appearing on the personal deviceselection buttons 236 represent devices sharing one of the possiblecommunication channels 160 of FIG. 13. Moreover, as noted above, thedevice selection screen 234 may be a function of a dedicated simplifieddata transfer application, of the operating system, or of anotherapplication, such as the media management application 90.

Turning to FIG. 19, a flowchart 238 describes an embodiment of a methodfor performing the initiation 124 in the manner indicated by FIGS.17-18. In a first step 240, the working device 120 or the personaldevice 122 may run smart data transfer software. As discussed above, thesmart data transfer software may represent, for example, a standaloneapplication or a function of the operating system. Either automaticallyor in response to a user selection, in step 242, the smart data transfersoftware on either the working device 120 or the personal device 122 mayinitiate network communication between the devices. The working device120 and the personal device 122 may communicate with one another by wayof any of the communication channels 160 illustrated in FIG. 13 above.As noted above with reference to FIG. 13, the communication channel 160which may be identified and established between the working device 120and the personal device 122 using a protocol such as Bonjour® by AppleInc. An additional or alternative embodiment for carrying out step 242is described in greater detail below with reference to FIG. 20.

In step 244, with communication between the working device 120 and thepersonal device 122 established, the communication-initiating device maycommunicate information to the other device to request a start of thesimplified data transfer 114. Step 244 may also include saving the userdata associated with the device state 62 of the working device 120 inpreparation for the forthcoming smart data transfer 128.

In a next step 246, the working device 120 and the personal device 122may communicate device profiles indicating the capabilities of eachdevice to one another. The device profiles exchanged in step 246 mayinclude a variety of data describing the capabilities of the personaldevice 122 and working device 120. For example, the device profiles mayinclude messages of any form, including extensible markup language(XML), which may denote the device name, serial number, owner name, typeof device, as well as other identifying information. The otheridentifying information may include, for example, a service user name.The device profiles may additionally denote capabilities of the personaldevice 122 or the working device 120 by indicating which applications,drivers, or services may be installed on each device.

Because the personal device 122 may already have stored a device profileassociated with the working device 120, and vice versa, the deviceprofiles may not be transferred. However, because the capabilities ofeither the working device 120 or the personal device 122 may change fromtime to time, the device profiles may be updated and transmitted to eachdevice on at least some occasions.

In step 248, the personal device 122 and the working device 120 may eachperform a device authentication process, which may be based at least inpart on the device profiles exchanged during step 246. During the deviceauthentication, the personal device 122 or the working device 120 maydetermine whether the other is trusted. The initiation 124 may becancelled if either the personal device 122 or the working device 120fails to authenticate the other in step 248

In a next step 250, the personal device 122 and the working device 120may scan for available network communication channels 160, other thanthe network communication channel 160 currently used for communication.In so doing, the personal device 122 and the working device 120 maydetermine that a higher bandwidth network may be available fortransferring data during the forthcoming smart data transfer 128.

In step 252, after scanning for the available network communicationchannels 160, the personal device 122 and the working device 120 mayexchange new network configuration information. As discussed above withreference to FIGS. 15 and 16, the network configuration information mayinclude, for example, XML messages denoting lists of networkcommunication channels 160 accessible via the working device 120 or thepersonal device 122. Among other things, the network configurationinformation may include known authorization keys and service setidentifier (SSID). By way of example, the network configurationinformation may include PAN interface 28 configuration information, suchas a Bluetooth serial number, MAC address, and an associated password,as well as LAN interface 30 configuration information, such as a WiFi IPaddress, a WiFi MAC address, and a WiFi SSID. The network configurationinformation may be stored for use at a later time to permit the personaldevice 122 and the working device 120 to ascertain a higher bandwidthconnection.

In steps 254 and 256, the personal device 122 and the working device 120may remain in communication to transfer additional information for theinitiation 124. In step 254, the working device 120 may transmit devicestate pointers to the personal device 122, which may describe the userdata of the working device 62 which may be transferred. The device statepointers may represent a message, such as an XML message, that includesthe filename, associated application, file size, or other relatedinformation associated with each file that may be transferred. Forexample, the other related information may include whether or not a filehas been read, a geographic location where the file was created ormodified using a convention such as GeoRSS, a related uniform resourcelocator (URL), the hierarchy of the application with which the file isassociated, the location of the application on the screen of the workingdevice 120 with which the file is associated, the last device whichmodified the file, etc. In step 256, the working device 120 may transfercertain low bandwidth elements associated with the user data of thedevice state 62 of the working device 120. Such low bandwidth elementsmay include, for example, thumbnail images of each file to betransferred or excerpts of data from each file.

Turning next to FIG. 20, a flow chart 258 illustrates an embodiment of amethod for initiating network communication for performing theinitiation 124 in the manner illustrated by FIGS. 17-18. As noted above,the flowchart 258 represents a more detailed description of step 242 ofthe flowchart 238 of FIG. 19.

In a first step 260, the working device 120 or the personal device 122may begin network communication using one of the network interfaces 26.As indicated by decision block 262, if the working device 120 and thepersonal device 122 are already connected, then the process flows tostep 264. In step 264, peer-to-peer communication between the workingdevice 120 and the personal device 124 begins.

Returning to decision block 262, if the devices are not alreadyconnected by way of one of the network communication channels 160, thepersonal device 122 or the working device 120 may attempt to communicateusing the most recently available network communication channel 160 atwhich the other device was available. As indicated by decision block268, if the attempt to communicate in step 266 results in a successfulconnection, the process may flow to step 264, and device communicationmay begin. If the connection attempted in step 266 is not successful,however, the process may flow to step 270.

In step 270, the working device 120 or the personal device 122 may firstconnect to the web service 170, as illustrated in FIG. 13. The workingdevice 120 or the personal device 122 may reach the web service 170 byway of the Internet 168 or directly via the WAN communication channels176 or 178. In step 272, the working device 120 or the personal device122 may perform authenticate itself with the web service 170 using anypredetermined security scheme.

In step 274, the working device 120 or the personal device 122 mayreceive the IP address of the other device from the web service 170. Asnoted above with reference to FIG. 13, the web service 170 may representa dynamic domain name system (DNS) service. Accordingly, the web service170 may maintain the current IP address of each device by communicatingwith a plugin associated with the simplified data transfer software oneach device.

Having obtained the IP address of the other device, the working device120 or the personal device 122 may locate the other over the Internet instep 276. In step 264, the working device 120 or the personal device 122may subsequently establish a peer-to-peer connection via the Internet168 to the other.

FIGS. 21-24 illustrate various embodiments related to the smart prompt126. Turning first to FIG. 21, a flowchart 278 illustrates an embodimentof a method for determining whether and which smart prompt to displaywhen the initiation 124 takes place via the NFC communication channel162. Embodiments of performing the initiation 124 via the NFCcommunication channel 162 are discussed above with reference to FIGS.14-16. For exemplary purposes, the method described by the flowchart 278represents the point of view of the handheld device 36, which may beeither the working device 120 or the personal device 122 of thesimplified data transfer system 118. It should be appreciated, however,that the method outlined by the flowchart 278 may be adapted to anyelectronic device 10 having the display 18.

Step 280 represents a response by the handheld device 36 to theinitiation 124 taking place via the NFC communication channel 162, asnoted above with reference to FIGS. 14-16. The operating system,hardware, or simplified data transfer software running on the handhelddevice 36 may initiate a determination of whether and which type ofprompt to issue following the exchange of NFC communication indicated inFIG. 15.

As indicated by decision block 282, the handheld device 36 may employthe device profiles 196 exchanged during the initiation 124 to assesswhether the other electronic device 10 is the computer 58. If thehandheld device 36 assesses that the other device is the computer 58,the process may proceed to a decision block 284. As indicated by thedecision block 284, if the handheld device 36 determines that the otherelectronic device 10 is owned by the same entity as the handheld device36, the process may continue to step 286.

In step 286, the handheld device 36 may issue a prompt to permit a userto determine whether to proceed to the smart data transfer 128 phase ofthe simplified data transfer system 118. If the user chooses to proceed,the handheld device 36 will either prepare to send data to or receivedata from the computer 58, depending on which device represents theworking device 120 and which device represents the personal device 122.

Returning to the decision block 284, if the computer 58 is notdetermined to have the same owner as the handheld device 36, the processmay instead flow to step 288. In step 288, the handheld device 36 mayissue a prompt to permit the user to pair the handheld device 36 and thecomputer 58. If the user chooses to pair the devices, the handhelddevice 36 and the computer 58 may thereafter be considered to share thesame ownership or may otherwise represent devices which may authenticateone another during the initiation 124.

With continued reference to FIG. 21, and returning to the decision block282, if the handheld device 36 does not determine the other electronicdevice 10 to be the computer 58, the process may instead flow to adecision block 290. In the decision block 290, the handheld device 36may assess whether the device is the standalone media player 64. If thedevice is the standalone media player 64, the process may flow to adecision block 292. In the decision block 292, the handheld device 36may determine whether the handheld device 36 and the standalone mediaplayer 64 are owned by the same entity. If so, the process flows todecision block 294.

In decision block 294, the handheld device 36 may determine whether thestandalone media player 64 is currently playing a media file. Suchinformation may have been conveyed to the handheld device 36 in thedevice profiles 196 or device state pointers 208 exchanged during theinitiation 124. If the standalone media player 64 is currently playing amedia file, the process may flow to step 296.

In step 296, the handheld device 36 may issue a prompt to permit a userto determine whether to proceed to the smart data transfer 128 phase ofthe simplified data transfer system 118. If the user chooses to proceed,the handheld device 36 will either prepare to send data to or receivedata from the standalone media player 64, depending on which devicerepresents the working device 120 and which device represents thepersonal device 122.

Returning to the decision block 292, if the standalone media player 64is not determined to have the same owner as the handheld device 36, theprocess may instead flow to step 298. Similarly, returning to thedecision block 294, if the handheld device 36 determines that thestandalone media player 64 is not playing a media file, the process mayalso flow to step 298.

In step 298, the handheld device 36 may issue a prompt to permit theuser to pair the handheld device 36 and the standalone media player 64.If the user chooses to pair the devices, the handheld device 36 and thestandalone media player 64 may thereafter be considered to share thesame ownership or may otherwise represent devices which may authenticateone another during the initiation 124.

With continued reference to FIG. 21, and returning to the decision block290, if the handheld device 36 does not determine the other electronicdevice 10 is the standalone media player 64, the process may flow to adecision block 300. In the decision block 300, the handheld device 36may determine whether the other electronic device 10 is another handhelddevice 36. If so, the process may flow to a decision block 302.

As indicated by the decision block 302, if the first handheld device 36determines that the second handheld device 36 is a known device and, asindicated by the decision block 304, the working device 120 isattempting to send data (e.g., by way of a data drop described belowwith reference to FIGS. 33-35), the process may flow to step 306.

In step 306, the first handheld device 36 may issue a prompt to permit auser to determine whether to proceed to the smart data transfer 128phase of the simplified data transfer system 118. If the user chooses toproceed, the first handheld device 36 will either prepare to send datato or receive data from the second handheld device 36, depending onwhich handheld device 36 represents the working device 120 and whichrepresents the personal device 122.

Returning to the decision block 302, if the second handheld device 36 isnot determined to have the same owner as the first handheld device 36,the process may instead flow to step 308. Similarly, returning to thedecision block 304, if the first handheld device 36 determines that thesecond handheld device 36 not sending data or is not prepared to receivedata, the process may also flow to step 308.

In step 308, the first handheld device 36 may issue a prompt to permitthe user to pair the first handheld device 36 and the second handhelddevice 36. If the user chooses to pair the devices, the first handhelddevice 36 and the second handheld device 36 may thereafter be consideredto share the same ownership or may otherwise represent devices which mayauthenticate one another during the initiation 124.

FIGS. 22A-B illustrate prompts which may issue in steps 286, 288, 296,298, 306, and 308 of the flowchart 278 of FIG. 21. Turning first to FIG.22A, a run simplified data transfer prompt 310 may include a series ofuser selectable buttons 312. At least one of the user selectable buttons312 may represent an option to proceed to the smart data transfer 128 byrunning, for example, a dedicated simplified data transfer application.

Turning next to FIG. 22B, a device pairing prompt 314 may similarlyinclude a number of user selectable buttons 316. At least one of theuser selectable buttons 316 may represent an option to pair the handhelddevice 36 with the other electronic device 10. If the user chooses topair the devices, the handheld device 36 and the other electronic device10 may thereafter be considered to share the same ownership or mayotherwise represent devices which may authenticate one another duringthe initiation 124.

FIG. 23 is a flowchart 318 describing another embodiment of a methodassociated with the smart prompt 126. The flowchart 318 may represent anembodiment of determining whether to issue the smart prompt 126following the initiation 124, whether the initiation 124 takes place viathe NFC communication channel 162 or via other network communicationchannels 160. It should be appreciated that the method outlined by theflowchart 318 may be adapted to any electronic device 10 having thedisplay 18.

Beginning with step 320, the working device 120 or the personal device122 may consider a variety of factors associated with the relationshipbetween the working device 120 and the personal device 122. Such factorsmay include, for example, the owner of the devices, whether the devicesare located on a trusted network, whether the devices share mediaregistration such as iTunes® registration, preferences of the owner(s)of the devices, a social network relationship between the owners of thedevices, a history of transactions between the devices, and othersecurity measures employed by the devices.

In the decision block 322, the factors are assessed to determine whetherthere is a trust relationship between the working device 120 and thepersonal device 122. If the factors do not indicate trust, the processmay flow to step 324. In step 324, the working device 120 or thepersonal device 122 may issue a context based prompt for transfer. Ifthe user chooses to proceed, the working device 120 may prepare to senddata and the personal device 122 may prepare to receive data in theforthcoming smart data transfer 128.

Returning to the decision block 322, if the factors do indicate trust inthe decision block 322, then the process may flow to step 326. In step326, the working device 120 or the personal device 122 may consider thecontext of the device state 62 data. In a decision block 158 whichfollows, if the data indicated in the device state pointers 208 alreadyresides on the personal device 122, the process may flow to step 330. Byway of example, if the device state pointers 208 indicate a particularmedia file, such as the song 104, is to be transferred, and the personaldevice 122 already has the media file, the process may flow to step 330.

In step 330, the smart prompt 182 may not issue, but the working devicemay instead transfer additional pointers related to the data whichalready resides on the personal device 120. For example, the workingdevice 120 may transfer only a cache file indicating a point in themedia where the media file was being played. Because no smart prompt 126is issued, the transfer of step 330 may take place over the NFCcommunication channel 162 immediately following the initiation 124.However, it should be appreciated that step 330 may additionally oralternatively take place over another communication channel 160, such asthe PAN communication channel 164 or the LAN communication channel 166.In this way, the personal device 122 may receive the cache file andbegin to play the media file at the point where the working device 120left off.

If the user data of the device state 62 does not already reside on thepersonal device 122, the process flow may continue to a decision block332. In the decision block 332, the personal device 122 may determinewhether there is only one application currently open on the workingdevice 120, as may be indicated by the device profiles exchanged duringthe initiation 124. If only one application is open on the workingdevice 120, then the process may flow to a decision block 334.

In the decision block 334, the personal device 122 may determine whetherthe size of the user data of the device state 62 is relatively small,which may be a preset threshold determined by user preferences (e.g.,less than 1 MB) or may vary depending on the bandwidth of availablenetwork communication channels 160. Moreover, whether the data is smallmay be determined based on design constraints, storage capabilities ofthe personal device 122, or other factors. If the user data of thedevice state 62 is small, the process may flow to step 336. In step 336,all of the user data associated with the device state 62 may beautomatically transferred in the forthcoming smart data transfer 128.

If, as indicated by the decision block 334, the data is not small, thenthe process flows to a decision block 338. According to the decisionblock 338, if one of the network communication channels 160 ofrelatively high bandwidth is available, the process may flow to step336, as described above. Whether one of the network communicationchannels 160 is of relatively high bandwidth which may be determinedfrom a preset threshold determined by user preferences (e.g., greaterthan 2 Mbit/s) or may vary depending on the amount of user dataassociated with the device 62 which is to be transferred. Moreover,whether the one of the network communication channels 160 is ofrelatively high bandwidth may be determined based on design constraints,network capabilities of the working device 120 or the personal device122, or other factors.

Returning to the decision block 338, if one of the network communicationchannels 160 of relatively high bandwidth is not available, the processmay instead flow to step 340. In step 340, the working device 120 or thepersonal device 122 may issue a prompt, such as that illustrated byFIGS. 24A-B and described below. The prompt may to allow a user toselect whether and which user data of the device state 62 of the workingdevice 120 is transferred to the personal device 122.

With continued reference to the flowchart 318 of FIG. 23, and returningto the decision block 332, if the personal device 122 determines thatmore than one open application is open on the working device 120 as ofthe initiation 124, the process may flow to a decision block 342. In thedecision block 342, the personal device 122 may determine whether theuser data associated with the topmost open application of the devicestate 62 is relatively small. As discussed above, whether the size ofthe user data of the device state 62 is relatively small may be a presetthreshold determined by user preferences (e.g., less than 1 MB) or mayvary depending on the bandwidth of available network communicationchannels 160. Whether the data is small may also be determined based ondesign constraints, storage capabilities of the personal device 122, orother factors.

As indicated by the decision block 342, if the user data associated withthe topmost open application of the device state 62 is small, theprocess may flow to a step 344. In step 344, the user data associatedwith the top most application opened in the device state 62 may beautomatically transferred or prepared for transfer. In a next step 346,the remaining user data of the device state 62 may be considered beforethe process may continue to the decision block 334. Similarly, returningto the decision block 342, if the user data associated with the topmostopen application of the device state 62 is not small, the process mayalso flow to the decision block 334.

FIGS. 24A-B represent a context-based prompt 348 which may be displayedbased on determinations made in the flowchart 318 of FIG. 23. Turningfirst to FIG. 24A, the context-based prompt 348 may include, forexample, a series of transfer selection buttons 350, 352, and 354. Thetransfer selection button 350 may allow a user to transfer all of theuser data associated with the device state 62 of the working device 120.The transfer selection button 352 may allow a user to select which userdata should be transferred from among a list of user data, describedfurther below with reference to FIG. 24B. The transfer selection button354 may cause the working device 120 to save the user data of the devicestate 62 for a later transfer, as described below with reference toFIGS. 31-34.

Turning next to FIG. 24B, if a user chooses the transfer selectionbutton 352, a corresponding prompt indicated by the numeral 355 mayappear. The prompt 355 may permit a user to choose which data is to betransferred from among the user data of the device state 62. The list ofuser data appearing on the prompt 352 of FIG. 24B may arise from thedevice state pointers which may be transferred to the personal device122 during the initiation 124.

In listing the user data, the prompt 355 may include a file name orother text descriptions 356. The text descriptions 356 may besupplemented by application descriptions 358, representing theapplications for which the files are designed. Images 360, which mayhave been received by the personal device 122 as low bandwidth elements,may represent, for example, an image describing the type of filerepresented by the user data or may include excerpts from each file ofuser data.

FIGS. 25-26 illustrate the smart data transfer 128 of the simplifieddata transfer system 118. Turning first to FIG. 25, a flowchart 362describes an embodiment of a method for performing the smart datatransfer 128 of the simplified data transfer system 118. In a first step364, the working device 120 and the personal device 122 may begin theselection of a network for transfer following the initiation 124 and thesmart prompt 126. The working device 120 and the personal device 122 mayconsider a variety of factors, which may include set by a user or bydefault, as discussed above with reference to FIGS. 12A-D.

By way of example, preferences for certain network communicationchannels 160 may be based on selections of whether to connect using thefastest available connection; whether to connect using only the Internetor not ever using the Internet; whether to connect using certainspecified encryption schemes or to require a passcode or passkey beforetransfer may occur; whether to require proximity based on the physicallocation of the electronic devices 10 (i.e., as determined by thelocation sensing circuitry 22); or whether to prefer a particular,specified connection to the particular device. The flowchart 362 forconducting the smart data transfer 128 may represent only one possibleembodiment of many, depending on preference settings such as thosediscussed above.

In a decision block 366, the working device 120 or the personal device122 may assess whether a local network communication channel 160, suchas the PAN communication channel 164, the LAN communication channel 166,or the wired I/O communication channel 180, is available. The assessmentof the decision block 366 may be facilitated by network configurationinformation previously exchanged during the initiation 124 phase.

As indicated by the decision block 366, if one of the available networkcommunication channels 160 is a local communication channel, the devicesmay establish a peer-to-peer or ad hoc connection using that networkcommunication channel 160 in step 368. If not, the process may insteadflow to step 370. In step 370, the working device 120 or the personaldevice 122 may connect to the web service 170. As discussed above withreference to FIG. 13, the working device 120 or the personal device 122may reach the web service 170 by way of the Internet 168 or directly viathe WAN communication channels 176 or 178. In step 372, the workingdevice 120 or the personal device 122 may perform a deviceauthentication with the web service 170 using any predetermined securityscheme.

In a subsequent step 374, the working device 120 or the personal device122 may receive the IP address of the other device from the web service170. As noted above with reference to FIG. 13, the web service 170 mayrepresent a dynamic domain name system (DNS) service. Accordingly, theweb service 170 may maintain the current IP address of each device bycommunicating with a plugin associated with the simplified data transfersoftware on each device. Having obtained the IP address of the otherdevice, the working device 120 or the personal device 122 may locate theother over the Internet 168 in step 368, establishing a peer-to-peer orad hoc connection.

In step 375, the working device 120 may convert certain elements of theuser data which is to be transferred. From the previous exchange ofdevice profiles, the working device 120 may assess whether the personaldevice 122 is capable of processing each element of user data. By way ofexample, the user data associated with the embodiment of the devicestate 62 of FIG. 7 may be set to be transferred. If the personal devicelacks a spreadsheet application 86 or presentation application 88, theworking device 120 may convert the spreadsheet 100 or the presentation102 to a form which the personal device 122 may process, such as animage file or PDF.

Additionally, the working device 120 may assess whether the personaldevice 122 has access to the Internet 168 based on the prior exchange ofdevice profiles and/or network configuration information. If thepersonal device 122 lacks access to the Internet 168 and is to be sent aweb page, the working device 120 may transfer a web archive of the webpage rather than only a URL pointing to the web page. Similarly, if thepersonal device 122 lacks access to the Internet 168 and is to be sentan online map, the working device 120 may first download informationabout a greater amount of territory than only the online map of thedevice state 62 of the working device 120. The working device 120 maythen transfer a web archive of the newly downloaded map to the personaldevice 122. In this way, a user of the personal device 122 may be ableto view more than only what the original online map displayed if theuser so desires.

Following step 375, the process may continue to step 376. In step 376,the working device 120 may begin to transfer the user data associatedwith its device state 62 to the personal device 122. The order oftransfer of the user data may be prioritized by a number of factors fromthe selection of preferences, as described above with reference to FIGS.12A-D. By way of example, the priority may be determined by preferenceselections of whether a file is associated with a productivity oroffice-related software product; whether a file represents user datacreated or modified by a particular user, such as the owner of thereceiving device; whether a file is within or in excess of a particularsize; which network communication channels may be available for thesmart data transfer 128; whether a file is capable of being processednatively by the receiving device; whether a file is of a particulartype; or whether a file is to be transferred from a particular device ora particular class of devices. It should also be appreciated that notall data may be transferred in step 376. Rather than transfer certainfiles larger than a predetermined size (e.g., 1 MB), the working device120 may instead only transfer a pointer to the data. The working device120 may transfer the entire file after receiving an instruction from thepersonal device 122.

Turning to decision block 377, if the data transfer is not interrupted,the transfer may continue until complete in step 378. However, if thedata transfer is interrupted, the process may flow from the decisionblock 377 to a decision block 379. In the decision block 379, theworking device 120 or the personal device 122 may attempt tore-establish the recently interrupted connection. If the connection isre-established, the process may return to the decision block 377,continuing to transfer data unless interrupted again.

If the recently interrupted connection is not re-established, theprocess may flow to a decision block 380. In the decision block 380, theworking device 120 and the personal device 122 may assess whetheranother network communication channel 160 is available. If so, a newconnection may be established in step 381. If another networkcommunication channel 160 is not available, then the process may flow tostep 382. In step 382, the working device 120 may instead save theremaining user data for transfer at a later time. Delayed transfer, asindicated by step 382, is described in greater detail below withreference to FIGS. 31-34.

Steps 376-382 may be explained by the following example. If a userinitiates the simplified data transfer system 118 while the workingdevice 120 and the personal device 122 are physically near one another,the initial transfer of data of step 376 may take place over a localnetwork communication channel 160, such as the PAN communication channel164 or the LAN communication channel 166. However, if the user laterseparates the working device 120 and the personal device 122, such thatthe devices become too far apart to continue the transfer, the workingdevice 120 may instead continue to transfer the data over anotherchannel, such as over the Internet 168 by way of the WAN communicationchannels 172 or 174. Alternatively, the working device 120 may save theremaining user data for transfer at a later time.

FIGS. 26-28 illustrate examples of responses by the personal device 122upon receipt of the user data following the smart data transfer 128.Turning first to FIG. 26A, a received data screen 384 may display a listof received data 385. The received data 385 represents user data of thedevice state 62 of the working device 120 that has been received by thepersonal device 122. A user may open the received data 385 by pressingon it, which may open the data in an associated mobile application.

As noted above with reference to step 375 of the flowchart 362 of FIG.25, certain data may be converted prior to transfer. Exemplifying such acondition, the received data 385 of the received data screen 384 mayinclude a presentation and spreadsheet which, because the personaldevice 122 may not be capable of processing the files in their nativeformats, may have been converted to and transferred as a PDF file. Thus,the received data screen 384 may indicate the files may be opened in aPDF reader on the personal device 122.

The personal device 122 may open the received data 385 using aparticular application based on the type of the data. For example, thepersonal device 122 may open a web archive or URL for an online map in amap-specific application, a web archive or URL for an online video in avideo-specific application, or a web archive or URL for a web page not amap or video in a web browser. The personal device 122 may open apointer to a media or playlist or may open a media file in a mediamanagement application. Certain productivity data may be opened inspecific applications as well, including .key files (associated withKeynote '08), which may be opened in an application such as iWorkReader, and .doc, .xls, and .ppt files that may be opened in anapplication such as Office Reader. Moreover, data associated with otherthird party developers may be opened with applications developedspecifically for the personal device 122.

Additionally, if the received data is particularly large, the workingdevice 120 may have only sent a pointer to the data. In such case, auser may select an option to download the large data. A series ofassociated received data icons 386 may provide additional images of orexcerpts from the received data 385.

An options button 387 and edit button 388 may allow a user to adjustvarious preferences, as discussed above with reference to FIGS. 12A-D.Using the options button 387 and the edit button 388, as well as certainpredetermined interface functions, a user may modify the list ofreceived data 385 in a variety of ways. For example, the user may deleteindividual list items by striking horizontally, as used in many othermobile device applications such as those used by the iPhone® by AppleInc. The user may delete all list items by tapping a trash can icon 390and pressing a button on a prompt to confirm. The user may refresh thelist by initiating another simplified data transfer 114 by selecting arefresh button 389. The refresh button 389 may initiate communication torestart the simplified data transfer 114, as discussed above withreference to FIGS. 17-20. If the user refreshes the list, the existinglist items may remain and may not be removed, even though the dataassociated with the device state 62 of the working device 120 may havechanged. In this way, every change of the device state 62 of the workingdevice 120 may only add to the list of received data 385 with eachrefresh.

It should also be appreciated that if the simplified data transferapplication is closed and the received data screen 384 is no longervisible, the list of received data 385 may remain. When the user lateropens the simplified data transfer application by selecting thesimplified data transfer application icon 40 from the home screen of thehandheld device 36, the list of received data will be the same.

Turning next to FIG. 26B, a visual received data screen 391 may displaythe list of received data 385 of the received data screen 384 in avisually appealing and intuitive manner. By way of example, the visualreceived data screen 391 may arise when a user tilts the handheld device36 after the handheld device 36 has received data in the smart datatransfer 128. The visual received data screen 391 may display arepresentation of the received data 385 using technology such as CoverFlow® by Apple Inc.

Using the visual received data screen 391, the user may quickly find thereceived data 385 the user wants to access. Visual descriptions 394 maydisplay an image describing the received data 385, providing, forexample, a screenshot or excerpt of the data of the device state 62 ofthe working device 120. A textual description 396 may provide, forexample, text indicating the name of the data, the application of theworking device 120 with which the data may have been associated, and/orthe application of the personal device 122 with which the data may beaccessed. With of flick of their fingers, the user may shuffle betweenthe visual descriptions 394 and associated textual description 396 toselect the received data 385 of their choice.

FIG. 27 is a flowchart 396 describing an embodiment of an alternativemethod for intelligently displaying user data associated with the devicestate 62. In a first step 398, the personal device 122 may receive theuser data associated with the device state 62 following the smart datatransfer 128. In step 400, the personal device 122 may consider thecontext associated with the user data. For example, in a decision block402, the personal device 120 may determine whether the user data issmall. Whether the size of the user data received is small may be apreset threshold determined by user preferences (e.g., less than 1 MB)or may be based on design constraints, storage capabilities of thepersonal device 122, or other factors. If the received data isdetermined to be small, the process may flow to a decision block 404.

As indicated by the decision block 404, if the user data is a map or aURL, the process may flow to step 406. In step 406, the map may bedisplayed in map software or the URL may be displayed in a web browseron the personal device 122. Alternatively, the personal device 122 mayprovide an indication that a map or a URL has been received. Returningto the decision block 404, if the user data of the device state 62 isnot a map or a URL, the process may flow to a decision block 408. In thedecision block 408, the personal device 122 may determine whether themap or the URL or the small user data is the only data received. If so,in a step 410, an appropriate application may open and display the userdata automatically. Alternatively, the personal device 122 may providean indication that user data for a particular application has beenreceived.

Returning to the decision block 408, if the small amount of user data isnot the only data received, the process may flow to step 412. In step412, the personal device 122 may provide an indication that the userdata has been received and may indicate which applications pertain tothe received user data.

With further reference to the flowchart 396 of FIG. 27, and returning tothe decision block 402, if the data received is not small, the processmay flow to a decision block 414. According to the decision block 414,the personal device 122 may determine whether only one file constitutesall of the received data. If so, in a step 416, the personal device 122may issue a prompt before opening the data in the appropriateapplication or may provide an indication that user data associated witha particular application has been received.

As indicated by the decision block 414, if the data is not the only datareceived, the process may flow to step 412. In step 412, the personaldevice 122 may provide an indication that the user data has beenreceived and may indicate which applications pertain to the receiveduser data.

FIG. 28 illustrates an embodiment of an indication screen 418 on thepersonal device 122 after the personal device 122 has received user datafrom the working device 120. As illustrated in FIG. 28, the indicationscreen 418 indicates that the personal device 122 has received userdata. By way of example, the indication screen 418 may indicate that theuser data received represents elements of the user data of theembodiment of the device state 62 of FIG. 7. The user data associatedwith the device state 62 may include, for example, the web page 96, theonline map 98, the spreadsheet 100, the presentation 102, the music file104, the playlist 106, and the video file 108. When such user data isreceived, the indication screen 418 may reflect that each of theelements of the device state 62 has been received by the personal device122.

As indicated by numeral 420, an icon for a web browser application maybe illuminated to indicate that the web page 96 has been received.Similarly, a map specific application icon 258 may be illuminated toindicate that the online map 98 has been received. Because, as describedabove, the personal device 122 may lack the capability to processnatively certain user data, such as the spreadsheet 100 or thepresentation 102, the user data may have been converted prior totransfer. Accordingly, the spreadsheet 100 and the presentation 102 mayhave been received by the personal device 122 as an image file or as aPDF. Thus, a photo application icon 424 may be illuminated to indicatethat the spreadsheet 100 and the presentation 102 have been received.

Finally, a media management application icon 426 may be illuminated toindicate that the music file 104, the playlist 106, and/or the videofile 108 have been received. Additionally, the simplified data transfericon 44 may be illuminated to indicate when any device state 62 userdata has been received. By selecting any of the illuminated icons, auser may view the user data received by the personal device 122.

Turning to FIG. 29, a flowchart 428 describes an exemplary embodiment ofa method for performing the simplified data transfer 114. By way ofexample, a user may be working on the computer 58 having a desktopinterface with a device state 62. The device state 62 of the computer 58may include a variety of open applications with associated data. Forexample, a web browser may display several web pages, such as a page ofthe New York Times, a page open to Google Maps, and a video playing onYouTube. A media management application such as iTunes® may be playing asong in a playlist, while a productivity application such as Keynote'08® may display a presentation and a digital content creationapplication such as Photoshop by Adobe may display a content creationfile such as a Photoshop file. If the user desires to leave theircomputer 58, they may use their handheld device 36 to “grab” all or aselection of the data currently open on the computer 58 using thesimplified data transfer 114.

In a first step 430, communication may be initiated between the handhelddevice 36 and the computer 58. As the computer 58 has data open in thedevice state 62 for the user to transfer, the computer 58 may representthe working device 120 and the handheld device 36 may represent thepersonal device 122. To begin, for example, the user may select thesimplified data transfer application icon 40, which may launchapplication and cause the prompt illustrated by FIG. 17C to be displayedon the handheld device 36. As shown in FIG. 17C, the prompt may includean option to begin to “grab” items on the computer 58.

Step 432 may begin when the user selects the option to begin to “grab”the items on the computer 58 and the handheld device 36 may send arequest to the computer 58 over the LAN communication channel 166. Therequest may be routed to the computer 58, rather than other electronicdevice 10, based on a preference set in the simplified data transferapplication. As noted above with reference to FIG. 17, the user mayselect the button labeled “Sources” to select a preference for thecomputer 58 to serve as the working device 120. It should also beappreciated, as noted above with reference to FIG. 13, that the list ofelectronic devices 10 visible to the handheld device 36 may be obtainedusing a device identification networking protocol such as Bonjour® byApple Inc. Alternatively, the request may be routed to the computer 58based on a preestablished secure pairing relationship between thehandheld device 36 and the computer 58.

With continued reference to step 432, the request sent from the handhelddevice 36 to the computer 58 may be received by at least one “listener”on the computer 58. The “listener” may be, for example, a standaloneapplication, a function of an operating system, or a function or pluginassociated with one or more of the applications of the device state 62of the computer 58. After receiving the request, the “listener” maygather information about the data open in the applications of the devicestate 62. If media is playing in a media management application, themedia may be paused.

In step 434, the “listener” on the computer 58 may transfer the devicestate pointers 208 to the handheld device 36. As noted above, the devicestate pointers 208 may provide various information about the dataassociated with the device state 62 of the working device 120. Thedevice state pointers 208 may be received all at once or in a staggeredfashion, as the “listener” application or applications transfers theinformation.

Step 436 may take place following or concurrently with step 434. As thedevice state pointers 208 are received, the handheld device 36 maydisplay each item in the smart prompt 126. In this case, the smartprompt 126 may resemble the prompt of FIGS. 26A-B and each item mayappear as it is received in the device state pointers 208.

With reference to the example introduced above, the smart prompt of step436 may display list the items of data associated with the device state62 of the computer 58 as follows. The New York Times web page may bedescribed with a page title, the URL of the web page, and an indicationthat selecting the item will open the web page in a mobile web browser,such as Safari® by Apple Inc. The YouTube video web page may bedescribed with a movie name, the URL of the movie, and an indicationthat selecting the item will open the video in a mobile online videoapplication, such as the YouTube application for the iPhone® by AppleInc. The Google Maps web page may be described with a location ordirection title, the URL of the map web page, an indication thatselecting the item will open the map in a mobile online map application,such as the Maps application for the iPhone® by Apple Inc.

As should be noted, the above-described data may be obtained from theInternet 168 from the URL provided by the device state pointers 208. Thedevice state pointers 208 may transfer such limited data to the handhelddevice 36 if the computer 58 determines that the handheld device 36 hasthe capability to access the Internet 168. It should be appreciated thatif the computer 58 does not determine that the handheld device 36 hasaccess to the Internet 168, the computer 58 may instead send webarchives of the above items in a subsequent transfer step describedbelow.

The song playing in the media management application may be describedwith a song name, a playhead pointer (indicating where in the song thecomputer 58 left off) and/or a playlist pointer, and an indication thatselecting the item will open the song in a mobile media managementapplication, such as the iPod application for the iPhone® by Apple Inc.If the user selects the item, the mobile media management applicationmay begin playing the song where the computer 58 left off and the nextsong may be the next song of the same playlist. It should be appreciatedthat the device state pointers 208 may send such limited information ifthe song and/or playlist already resides on the handheld device 36. Ifthe song is not available on the handheld device 36, the computer 58 mayalternatively send the entire song in the subsequent transfer stepdescribed below.

The presentation may be described with a file name and an indicationthat selecting the item will download the file. Similarly, the contentcreation file may also be described with a file name and an indicationthat selecting the item will download the file. Selecting either itemmay cause the handheld 36 to send a request to the computer 58 todownload the selected item.

With continued reference to the flowchart 428 of FIG. 29, step 438 maytake place if certain items are selected. For example, if the userselects the content creation file for download, the computer 58 mayfirst convert the file to PDF.

In a subsequent step 440, the computer 58 may transfer any data that hasbeen selected for download by a user or, alternatively, web archives,songs, or other data that may not be accessible to the handheld device36. In step 442, after the data has been transferred in step 440, theprompt may indicate that the data has been received by changing certainstatus indications. For example, after the presentation file isreceived, the prompt may indicate that selecting the item will open thepresentation in a mobile reader application such as iWork Reader byApple Inc. Similarly, after the content creation file (in PDF form) hasbeen received, the prompt may indicate that selecting the item will openthe file in a mobile PDF reader application.

Turning to figure FIG. 30, a flowchart 44 describes an embodiment of amethod for a user to perform the simplified data transfer 114 using thesimplified data transfer system 118. In a first step 446, a user mayactivate two electronic devices 10 configured to perform the simplifieddata transfer techniques disclosed herein. In step 448, the user mayopen at least one application on one of the devices. The electronicdevice 10 having the open application may be considered the workingdevice 120 and the other electronic device 10 may be considered thepersonal device 122.

In step 450, the user may, for example, begin the simplified datatransfer 114 by tapping the two devices together near their respectiveNFC interfaces 34. In doing so, the personal device 122 and the workingdevice 120 may begin communication associated with the initiation 124.In step 452, once the personal device 122 or the working device 120 hasissued the smart prompt 126, the user may select an option to runsimplified data transfer software. Finally, in step 454, the user mayreceive data from the working device 120 on the personal device 122.

FIGS. 31A-B illustrate alternative embodiments of the simplified datatransfer system 118 in which the smart data transfer 128 may be delayedfrom the time that the initiation 124 or smart prompt 126 may occur.Turning first to FIG. 31A, a delayed simplified data transfer system 456may represent an alternative embodiment of the simplified data transfersystem 118. In the delayed simplified data transfer system 456,following the initiation 124 and smart prompt 126 phases, the workingdevice 120 may save, rather than immediately transfer, user dataassociated with the device state 62. The user data may be saved in themain memory 14 or nonvolatile storage 16 of the working device 120.

At a later time, the working device 120 may transfer the user dataassociated with the device state 62 from its main memory 14 or itsnonvolatile storage 16 to the remote personal device 122 via apeer-to-peer connection over the Internet 168. As the personal device122 is remote from the working device 122, the personal device 122 maybe connected to the Internet 168 by way of the LAN interface 30 or theWAN interface 32. As should be appreciated, to form a peer-to-peerconnection over the Internet 168, the working device 120 or the personaldevice 122 may first poll the web service 170. As noted above withreference to FIG. 13, the web service 170 may represent a dynamic domainname system (DNS) service, which may maintain the current IP address ofeach device by communicating with a plugin associated with thesimplified data transfer application residing on each device. By way ofexample, the web service 170 may be a function of the Back to My Mac™service from Apple, Inc.

Turning next to FIG. 31B, an alternative delayed simplified datatransfer system 458 may represent another alternative embodiment of thesimplified data transfer system 118. In the delayed simplified datatransfer system 458, following the initiation 124 and smart prompt 126phases, the working device 120 may transfer user data associated withthe device state 62 to remote storage 460. The remote storage 460 mayrepresent a server for storing data remotely, and may be associated withthe web service 170.

At a later time, the remote storage 460 may transfer the user data tothe remote personal device 122 via a peer-to-peer connection over theInternet 168. As the personal device 122 is remote from the remotestorage 460, the personal device 122 may be connected to the Internet168 by way of the LAN interface 30 or the WAN interface 32. As should beappreciated, to form a peer-to-peer connection over the Internet 168,the working device 120 or the personal device 122 may first poll the webservice 170. The web service 170 may represent a dynamic domain namesystem (DNS) service, which may maintain the current IP address of theremote storage 460. By way of example, the web service 170 may be afunction of the Back to My Mac® service from Apple, Inc.

FIGS. 32A-B represent embodiments of methods of employing the delayedsimplified data transfer systems 456 and 458 of FIGS. 31A-B. Turningfirst to FIG. 32A, a flow chart 462 may describe an embodiment of amethod for the delayed simplified data transfer system 456 of FIG. 31A.In a first step 464, the initiation 124 may take place, and in a nextstep 466, the personal device 122 or the working device 120 may issuethe smart prompt 126.

In step 468, the smart data transfer 128 may take place. However, ratherthan transfer the user data associated with the device state 62 of theworking device 120 directly to the personal device 122, the workingdevice 120 may instead save the user data in its main memory 14 or thenonvolatile memory 16. In step 470, at a later time, the working device120 may transfer all or part of the user data associated with the devicestate 62 from its main memory 14 or nonvolatile memory 16 to thepersonal device 122. Because the working device 120 and the personaldevice 122 may be located remotely from one another, the devices mayfirst establish a peer-to-peer connection by way of the internet 168.

As should be appreciated, to form a peer-to-peer connection over theInternet 168, the working device 120 or the personal device 122 mayfirst poll the web service 170. As noted above with reference to FIG.13, the web service 170 may represent a dynamic domain name system (DNS)service, which may maintain the current IP address of each device bycommunicating with a plugin associated with the simplified data transferapplication residing on each device. By way of example, the web service170 may be a function of the Back to My Mac® service from Apple, Inc.

Turning next to FIG. 32B, a flow chart 472 may describe an embodiment ofa method for the delayed simplified data transfer system 458 of FIG.31B. In a first step 474, the initiation 124 may take place, and in anext step 476, the personal device 122 or the working device 120 mayissue the smart prompt 126.

In step 478, the smart data transfer 128 may take place. However, ratherthan transfer the user data associated with the device state 62 of theworking device 120 directly to the personal device 122, the workingdevice 120 may instead transfer the user data to the remote storage 460.As noted above, the remote storage 460 may represent a server forstoring data remotely, and may be associated with the web service 170.In step 480, at a later time, the remote storage 460 may transfer all orpart of the user data which it received from the working device 120.Because the remote storage 460 and the personal device 122 may belocated remotely from one another, the devices may first establish apeer-to-peer connection by way of the internet 168.

As should be appreciated, to form a peer-to-peer connection over theInternet 168, the personal device 122 may first poll the web service170. The web service 170 may represent a dynamic domain name system(DNS) service, which may maintain the current IP address of the remotestorage 460. By way of example, the web service 170 may be a function ofthe Back to My Mac® service from Apple, Inc.

FIGS. 33A-C represent block diagrams of an alternative embodiment of thesimplified data transfer system 118 in which user data associated withthe device state 62 of the working device 120 may be transferred to adestination device 484 by way of the personal device 122. As should beappreciated, the embodiments illustrated by FIGS. 33A-C reflect theembodiments illustrated in FIGS. 9A-F and discussed above.

Turning first to FIG. 33A, a three device simplified data transfersystem 482 may involve transferring data associated with the devicestate 62 of the working device 120 to the destination device 484 by wayof the personal device 122. In a first simplified data transfer 114between the working device 120 and the personal device 122, the workingdevice 120 may transfer the device state pointers 208, the deviceprofiles 196, and/or the network configuration information 206 to thepersonal device 122.

After transferring the device state pointers 208, the device profiles196, and/or the network configuration information 206 to the personaldevice 122, the working device 120 may or may not transfer the user dataassociated with the device state 62 of the working device 120 to thepersonal device 122. Instead, the working device 120 may save the userdata associated with the device state 62 for a later transfer in itsmain memory 14 or nonvolatile storage 16.

The personal device 122 may thereafter initiate another simplified datatransfer 114 between the personal device 122 and the destination device484. In so doing, the personal device may initiate a “drop” with thedestination device 484. As described below with reference to FIGS.35A-B, the drop function may be similar to the initiation 124, with theexception that the drop function may transfer data from the personaldevice 122, rather than to the personal device 122. In performing thedrop with the destination device 484, the personal device 122 maytransfer the device state pointers 208 or, alternatively, the deviceprofile 196 of the working device, to the destination device 484.

Using information received in the device state pointers 208, the deviceprofiles 196, and/or the network configuration information 206, thedestination device 484 may request the user data of the device state 62from the working device 120. The working device 120 may subsequentlytransfer the user data from its main memory 14 or nonvolatile storage 16to the destination device 484.

Turning next to FIG. 33B, a three device simplified data transfer system486 may involve transferring data associated with the device state 62 ofthe working device 120 to the destination device 484 by way of thepersonal device 122. In a first simplified data transfer 114 between theworking device 120 and the personal device 122, the working device 120may transfer the device state pointers 208, the device profiles 196,and/or the network configuration information 206 to the personal device122, subsequently transferring the user data of its device state 62 tothe personal device 122.

The personal device 122 may thereafter initiate another simplified datatransfer 114 between the personal device 122 and the destination device484. In so doing, the personal device may initiate a “drop” with thedestination device 484. As described below with reference to FIGS.35A-B, the drop function may be similar to the initiation 124, with theexception that the drop function may transfer data from the personaldevice 122, rather than to the personal device 122. In performing thedrop with the destination device 484, the personal device 122 maytransfer the device state pointers 208, the device profiles 196, and/orthe network configuration information 206, as well as the user dataassociated with the device state 62 of the working device 120.

Turning to FIG. 33C, a three device simplified data transfer system 488may involve transferring data associated with the device state 62 of theworking device 120 to the destination device 484 by way of the personaldevice 122. In a first simplified data transfer 114 between the workingdevice 120 and the personal device 122, the working device 120 maytransfer the device state pointers 208, the device profiles 196, and/orthe network configuration information 206 to the personal device 122.

After transferring the device state pointers 208, the device profiles196, and/or the network configuration information 206 to the personaldevice 122, the working device 120 may or may not transfer the user dataassociated with the device state 62 of the working device 120 to thepersonal device 122. Instead, the working device 120 may transfer theuser data associated with the device state 62 to the remote storage 460for a later transfer.

The personal device 122 may thereafter initiate another simplified datatransfer 114 between the personal device 122 and the destination device484. In so doing, the personal device may initiate a “drop” with thedestination device 484. As described below with reference to FIGS.35A-B, the drop function may be similar to the initiation 124, with theexception that the drop function may transfer data from the personaldevice 122, rather than to the personal device 122. In performing thedrop with the destination device 484, the personal device 122 maytransfer the device state pointers 208, the device profiles 196, and/orthe network configuration information 206 to the destination device 484.

Using information received in the device state pointers 208, the deviceprofiles 196, and/or the network configuration information 206, thedestination device 484 may request the user data of the device state 62from the remote storage 460. The remote storage 460 may subsequentlytransfer the user data to the destination device 484

FIGS. 34A-C represent embodiments of methods for employing the threedevice simplified data transfer systems 482, 486, and 488 of FIGS.33A-C. Turning first to FIG. 34A, a flow chart 490 may describe anembodiment of a method for the three device simplified data transfersystems 482 of FIG. 33A. In a first step 492, the working device 120 andthe personal device 122 may begin the initiation 124 and, in asubsequent step 494, the working device 120 may transfer the devicestate pointers 208, the device profiles 196, and/or the networkconfiguration information 206 to the personal device 122.

In step 496, the working device 120 may save the user data associatedwith the device state 62 to its main memory 14 or nonvolatile storage16. In step 498, the personal device 122 may thereafter initiate anothersimplified data transfer 114 between the personal device 122 and thedestination device 484. In so doing, the personal device may initiate a“drop” with the destination device 484. As described below withreference to FIGS. 35A-B, the drop function may be similar to theinitiation 124, with the exception that the drop function may transferdata from the personal device 122, rather than to the personal device122. In performing the drop with the destination device 484, in step500, the personal device 122 may transfer the device state pointers 208,the device profiles 196, and/or the network configuration information206 to the destination device 484.

In step 502, using information received in the device state pointers208, the device profiles 196, and/or the network configurationinformation 206, the destination device 484 may request the user data ofthe device state 62 from the working device 120. The working device 120may subsequently transfer the user data from its main memory 14 ornonvolatile storage 16 to the destination device 484.

Turning next to FIG. 34B, a flow chart 504 may describe an embodiment ofa method for the three device simplified data transfer systems 486 ofFIG. 33B. In a first step 506, the working device 120 and the personaldevice 122 may begin the initiation 124 and, in a subsequent step 508,the working device 120 may transfer the device state pointers 208, thedevice profiles 196, and/or the network configuration information 206 tothe personal device 122.

In step 510, the working device 120 may transfer user data associatedwith the device state 62 to the personal device 122. In step 512, thepersonal device 122 may thereafter initiate another simplified datatransfer 114 between the personal device 122 and the destination device484. In so doing, the personal device may initiate a “drop” with thedestination device 484. As described below with reference to FIGS.35A-B, the drop function may be similar to the initiation 124, with theexception that the drop function may transfer data from the personaldevice 122, rather than to the personal device 122. In performing thedrop with the destination device 484, in step 514, the personal device122 may first transfer the device state pointers 208, the deviceprofiles 196, and/or the network configuration information 206 to thedestination device 484. In a subsequent step 516, the personal device122 may transfer the user data associated with the device state 62 ofthe working device 120 to the destination device 484.

Turning to FIG. 34C, a flow chart 518 may describe an embodiment of amethod for the three device simplified data transfer systems 488 of FIG.33C. In a first step 520, the working device 120 and the personal device122 may begin the initiation 124 and, in a subsequent step 522, theworking device 120 may transfer the device state pointers 208, thedevice profiles 196, and/or the network configuration information 206 tothe personal device 122.

In step 524, the working device 120 may transfer the user dataassociated with the device state 62 to the remote storage 460. In step526, the personal device 122 may thereafter initiate another simplifieddata transfer 114 between the personal device 122 and the destinationdevice 484. In so doing, the personal device may initiate a “drop” withthe destination device 484. As described below with reference to FIGS.35A-B, the drop function may be similar to the initiation 124, with theexception that the drop function may transfer data from the personaldevice 122, rather than to the personal device 122. In performing thedrop with the destination device 484, in step 528, the personal device122 may transfer the device state pointers 208, the device profiles 196,and/or the network configuration information 206 to the destinationdevice 484.

In step 530, using information received in the device state pointers208, the device profiles 196, and/or the network configurationinformation 206, the destination device 484 may request the user data ofthe device state 62 from the remote storage 460. The remote storage 460may thereafter transfer the user data to the destination device 484.

FIGS. 35A and B illustrate an embodiment of performing a “drop” from thepersonal device 122 to the destination device 460. Turning first to FIG.35A, a data drop screen 532 may include a prompt for dropping user datafrom the personal device 122 to the destination device 484. The datadrop screen 532 may include user selectable buttons 534, 536, and 538.The user selectable button 534 may allow a user to choose to transferall user data that may have previously been transferred to the personaldevice 122 to the destination device 484. Similarly, the user selectablebutton 536 may allow a user to choose which data may be transferred tothe destination device 484. To cancel the transaction, a user may choosethe user selectable button 538. If the transaction is cancelled, theuser data may remain on the personal device 122 and may not transferredto the destination device 484 unless the drop is initiated a secondtime.

Turning next to FIG. 35B, a select-from-list screen 539 may arise whenthe user selectable button 536 is chosen by a user. The select-from-listscreen 539 may list user data 540 that may be selected to be “dropped”to the destination device 484 by a user. The user data 540 may bedescribed based on a file name or other text descriptions 542, which mayadditionally list the applications for which the files are designed.Images 544 may have been delivered to the personal device 122 as lowbandwidth elements 210 and may represent the type of file represented bythe user data 540 or an excerpt of the user data 540.

Turning to FIG. 36, a flowchart 546 illustrates an embodiment of amethod of using the simplified data transfer techniques described aboveamong three electronic devices 10. In a first step 548, a user mayactivate two devices having smart data transfer software. In step 550,the user may open at least one application on the first electronicdevice 10. In step 552, the user may tap the devices together toinitiate communication by way of NFC of the NFC communication channel162. As such, the electronic device 10 having the open application mayrepresent the working device 120 and the other electronic device 10 mayrepresent the personal device 122.

In a decision block 554, the working device 120 or the personal device122 may issue the smart prompt 126. As discussed above, the smart prompt126 may or may not issue depending on a variety of factors. As indicatedby the decision block 554, if the prompt does issue, the process mayflow to step 556. In step 556, the user may choose to run the smart datatransfer software to enter the smart data transfer 128 phase. Followingstep 556, or if the prompt does not issue, the process flows to step558.

In step 558, the user may receive the user data associated with thedevice state 62 of the working device 120 on the personal device 122.Alternatively, the user may receive only the device state pointers 208.In step 560, the user may activate a third electronic device 10configured for the simplified data transfer techniques described above.

In a subsequent step 562, the user may tap the personal device 122 tothe third electronic device 10 to initiate communication by way of theNFC communication channel 162. In so doing, the third electronic device10 may represent the destination device 484.

In a decision block 564, the personal device 122 or the destinationdevice 484 may issue the smart prompt 126. As discussed above, the smartprompt 126 may or may not issue depending on a variety of factors. Asindicated by the decision block 564, if the prompt does issue, theprocess may flow to step 566. In step 566, the user may choose to runthe smart data transfer software to initiate a “drop” onto thedestination device. Following step 566, or if the prompt does not issue,the process flows to step 558.

In step 568, the user may drop the user data associated with the devicestate 62 of the working device 120 onto the destination device 484 byway of the personal device 122. Alternatively, the user may drop onlythe device state pointers 208 onto the destination device 484, to allowthe destination device 484 to receive the user data associated with thedevice state 62 of the working device 120 directly from the workingdevice 120 or from the remote storage 160.

Many variations on the disclosed techniques may be employed to enable auser to transfer data between devices in a simplified manner. FIGS.37-38 represent one variation of the above-described techniques, inwhich the personal device 122 may obtain data from a partial devicestate of the working device 120 via the remote storage 460. FIGS. 39-41represent another variation of the above-described techniques, in whichthe personal device 122 may obtain the data from the partial devicestate via the remote storage 460, as well as obtain other data from thedevice state via the working device 120 directly. FIGS. 43-47 representscreens that may be displayed on the working device 120 or the personaldevice 122 regarding the variations of the above-described techniques.

Turning first to FIG. 37, a transfer diagram 570 illustrates a manner inwhich the personal device 122 may obtain data from a partial devicestate of the working device 120 via the remote storage 460. In thetransfer diagram 570, rather than transfer the entire device state 62,the working device 120 may transfer only certain selected elements ofthe device state 62, referred to herein as a partial device state 572.The partial device state 572 may include files that are recently openedand/or saved, web history, music, photos, etc. By way of example, thepartial device state 62 may be sent to the remote storage 460 by astandalone application, a function integrated into an existingapplication (e.g., the media management application 90 or the backupapplication 94), or a function integrated into the operating system ofthe working device 120.

Sending only the partial device state 572 may limit the total amount ofdata retained by the remote storage 460 at a given time. To furtherlimit excessive data stored on the remote storage 460, total availablestorage and the amount of time that the partial device state 572 isretained by the remote storage 460 may be limited. For example, theremote storage 460 may limit each user to approximately 500 MB and mayretain the partial device state 572 for up to 5 days.

To retrieve an individual item of the partial device state 572 of theworking device 120, the personal device 122 may download a list ofpartial device state pointers 574 from remote storage 460 upon thelaunch of the simplified data transfer application. The partial devicestate pointers 574 may represent an index of the partial device state572 that may reside on the remote storage 460. The simplified datatransfer application may enable the personal device 122 to selectindividual files from the partial device state 572. The personal device122 may send a request 576 for a selected item based on the partialdevice state pointers 574, and the remote storage 460 may respond bytransferring the request element 578 to the personal device 122. Itshould be appreciated that the working device 120 and the personaldevice 122 may connect to the remote storage 460 over the Internet 168in the manner described in FIG. 13.

FIG. 38 represents a flowchart 580 describing a technique for carryingout a simplified data transfer in the manner of FIG. 38. In a first step582, the working device 120 may periodically transfer the partial devicestate 572 to the remote storage 460. By way of example, the workingdevice 120 may encrypt and transfer certain elements of the device state62 as a user of the working device 120 views or makes changes to thefiles. For example, as the user opens or saves documents, opens or viewsweb pages, listens to music, or views photos, such files may beencrypted and transferred as the partial device state 572 to the remotestorage 460. The remote storage 460 may retain the partial device state572 from the working device 120 for a limited time (e.g., five days) andwith limited storage capacity (e.g., 500 MB/user).

When a user of the personal device 122 desires to remotely obtain a filerecently viewed or saved on the working device 120, the user may launchthe simplified data transfer application on the personal device 122 instep 584. In step 586, the personal device 122 may download the partialdevice state pointers 574, which may represent an index of all filesuploaded to the remote storage 460 by the working device 120 during themost recent five days. The simplified data transfer application maydisplay the partial device state pointers 574 in a manner sufficient toenable the user of the personal device 122 to select the desired file.In step 588, after the user has selected the desired file, the personaldevice 122 may download the file by requesting the file from the remotestorage 460, which may thereafter transfer the file to the personaldevice 122.

As noted above, FIGS. 39-41 represent another variation of theabove-described techniques, in which the personal device 122 may obtainthe data from the partial device state via the remote storage 460, aswell as obtain other data from the device state via the working device120 directly. Turning first to FIG. 39, a flowchart 590 describes atechnique for using the web service 170 to establish a direct connectionbetween the working device 120 and the personal device 122 via theInternet 168. In a first step 592, an application on the working device120 may determine the internet protocol (IP) address of the workingdevice 120 as assigned by an Internet service provider (ISP) that may beproviding Internet access to the working device 120.

In step 594, having obtained the IP address of the working device 120,the application running on the working device 120 may establishcommunication with the web service 170. The web service 170 may maintaina domain name system (DNS) registry of working devices 120. Theapplication running on the working device 120 may update the DNSregistry of the web service 170 to accurately reflect the IP addressdetermined in step 592.

If a user desires to establish a direct connection between the user'spersonal device 122 and working device 120, the personal device 122 maycontact the web service 170 in step 596. The personal device 122 mayrequest the IP address of the working device 120 from the DNS registryof the web service 170. In step 598, after obtaining the IP address ofthe working device 120, the personal device 122 may connect to theworking device 120 using the retrieved IP address and a predeterminedport number. Thus, the method of the flowchart 590 may enable thepersonal device 122 to establish a direct connection to the workingdevice 120.

Turning to FIG. 40, a simplified transfer diagram 600 illustrates amanner in which the direct connection described in the flowchart 590 mayenhance the simplified data transfer techniques of FIGS. 37-38. In thesimplified transfer diagram 600, the personal device 122 may retrievefiles from the partial device state 572 from the remote storage 460 inthe manner of FIG. 37. Using the method of the flowchart 590, however,the personal device 122 may further establish a direct connection to theworking device 122. Thus, as illustrated in the simplified transferdiagram 600, the personal device 122 may additionally retrieve filesfrom the device state 62 of the working device, which may notnecessarily be present in the partial device state 572 of the remotestorage 460.

To retrieve such files, the personal device 122 may initially launch thesimplified data transfer application. During an initialization, thesimplified data transfer application on the personal device 122 maydownload the device state pointers 208 directly from the working device122. In combination with the partial device state pointers 574downloaded from the remote storage 460, the personal device may thus becapable of retrieving a variety of files. When the user selects a givenfile to retrieve, the personal device 122 may contact either the workingdevice 122 with a request 602 or the remote storage 460 with a request576, depending on where the requested file may be located. If the fileis found only on the working device 122, the working device 122 mayrespond by transferring the requested file in a message 604. Otherwise,the remote storage 460 may transfer the requested file in a message 578.

FIG. 41 represents a flowchart 606, which may describe a method forcarrying out a simplified data transfer in the manner of FIG. 40. Steps608, 610, and 612 of the flowchart 606 may take place in substantiallythe same manner as steps 582, 584, and 586 of the flowchart 580 of FIG.38. However, in step 614, the personal device 122 may additionallyestablish a direct connection to the working device 120 using the methodof the flowchart 590 if the working device 120 is currently on andavailable over the Internet. In a subsequent step 616, the personaldevice 122 may download from the working device 122 the list of devicestate pointers 208, which may include files not available in the partialdevice state 572 that may reside on the remote storage 460.

Upon completion of step 616, the personal device 122 may display a mixedlist of files from both the partial device state pointers 574 from theremote storage 460 and the device state pointers 208 from the workingdevice 120. A user may be able to select a desired file from among thelist. In step 618, the personal device 122 may request and receive thedesired file from either the working device 120 or the remote storage460.

FIGS. 42-47 may represent screens that may be displayed on the workingdevice 120 or the personal device 122 while performing the techniquesdescribed above. Particularly, FIGS. 42-43 may represent preferences foran application that may run on the working device 120 to periodicallytransfer the partial device state 572 to the remote storage 460. FIGS.44-47 may represent screens displayed on the personal device 122 whiledisplaying the partial device state pointers 574 from the remote storage460 or the device state pointers 208 from the working device 120.

Turning to FIG. 42, a preference screen 620 may be displayed on anapplication running on the working device 120 to determine settings forperiodically updating the remote storage 460 with the partial devicestate 572. The screen 620 may include a series of list items 622 havingcorresponding checkboxes 624. The list items 622 and correspondingcheckboxes 624 may enable a user to select particular file types thatmay be encrypted and sent to the remote storage 460 from the workingdevice 120. Such file types may include, for example, web pages;Microsoft Office documents; PDF documents; iWork® documents; iPhoto®files based on events, such as the last imported photos or recentlyviewed photos; or iTunes files based on events, such as iTunes mediafiles recently purchased or recently played, or files among the top 25files played on the working device 120. A button 626 may enable a userto set whether or not the working device 120 may periodically update theremote storage 460, and a button 628 may enable the user to lock desiredsettings in place. A button 630, labeled “Advanced . . . ,” may enablecertain advanced preferences, as described below.

FIG. 43 may illustrate a screen 632 that may be displayed when a userselects the button 630, labeled “Advanced . . . ” The screen 632 maydisplay a series of list items 634, which may represent selected foldersof the working device 120 that may not be included in the transfer ofthe partial device state 572. For example, such list items 634 mayinclude folders containing private documents, banking documents, iChat®conversations, email messages, or certain work-related files. A button636 may enable the user to exclude additional folders by adding them tothe list items 634.

Similarly, a button 638 may enable the user to delete any of the listitems 634 that the user may want synchronized onto the remote storage460. To conclude any changes to the screen 632, the user may select abutton 640, labeled “Done.”

It should be appreciated that the functionality provided by the softwaredescribed in FIGS. 42-43 may be implemented in a variety of ways. Forexample, rather than include all functionality in a single applicationon the working device 120, the functionality may be distributed acrossmany applications. A photo management application, such as iPhoto®, mayautomatically cache recently viewed or modified image files to theremote storage 460; a media management application, such as iTunes®, mayautomatically cache recently played songs to the remote storage 460; aweb browser, such as Safari®, may automatically cache recently viewedweb pages to the remote storage 460; and/or productivity software, suchas Keynote®, may automatically cache recently viewed or modifieddocuments to the remote storage 460.

FIGS. 44A-D may illustrate screens that may be displayed on the personaldevice 122, representing how different types of files from the devicestate 62 of the working device 120 or the partial device state 572residing on the remote storage 460 may be obtained on the personaldevice 122. Turning first to FIG. 44A, a screen 642 may represent a homescreen of the personal device 122, which may be, for example, thehandheld device 40. When the simplified data transfer application icon40 is selected, the simplified data transfer application may launch. Asshould be appreciated, upon the launch of the simplified data transferapplication, the personal device 122 may download the partial devicestate pointers 572 from the remote storage 460 and/or the device statepointers 208 from the working device 120.

As illustrated in FIG. 44B, the handheld device 40 may display a screen644 when the icon 40 is selected. The screen 644 may include a series oficons 646-652, respectively labeled “Documents,” “Web,” “Photos,” and“Music.” As shown in FIG. 44B, the screen 644 may be displayed when theicon 646 labeled “Documents” is selected and highlighted, and acorresponding series of list items 654 may represent various types ofdocument files from the partial device state pointers 572 or the devicestate pointers 208. A button 655, labeled “Settings,” may enable theuser to enable certain settings, as described above with reference toFIG. 12.

Selecting the list item 654 labeled “Keynote” may cause the handhelddevice 40 to display a screen 656, as illustrated in FIG. 44C. Thescreen 656 may include list items 658 representing Keynote®presentations that may reside on either the remote storage 460 or theworking device 120. A button 660 may enable the user to navigate back tothe screen 644 of FIG. 44B. When the user selects from among the listitems 658, the personal device 122 may request and receive the selectedfile from either the working device 120 or the remote storage 460. Byway of example, the user may select the list item 658 labeled “MarketingEvent.” In response, the personal device 122 may download thecorresponding presentation file. As illustrated by a screen 662 of FIG.44D, the selected presentation file may thereafter be displayed on thepersonal device 122.

FIGS. 45A-C may also illustrate screens that may be displayed on thepersonal device 122, representing how different types of files from thedevice state 62 of the working device 120 or the partial device state572 residing on the remote storage 460 may be obtained on the personaldevice 122. Turning first to FIG. 45A, a user may select the simplifieddata transfer application icon 40 of the screen 642, which may cause thesimplified data transfer application may launch. As should beappreciated, upon the launch of the simplified data transferapplication, the personal device 122 may download the partial devicestate pointers 572 from the remote storage 460 and/or the device statepointers 208 from the working device 120.

As illustrated in FIG. 45B, the handheld device 40 may display a screen664 when the icon 40 is selected and the icon 648, labeled “Web,” isalso selected. A corresponding series of list items 666 may representvarious types of web-related files from the partial device statepointers 572 or the device state pointers 208. The button 655, labeled“Settings,” may enable the user to enable certain settings, as describedabove with reference to FIG. 12.

Selecting the list item 666 labeled “Web Pages” may cause the handhelddevice 40 to display a screen 668, as illustrated in FIG. 45C. Thescreen 668 may include list items 670 representing recently viewed webpages that may reside on either the remote storage 460 or the workingdevice 120. A button 672 may enable the user to navigate back to thescreen 644 of FIG. 44B. When the user selects from among the list items658, the personal device 122 may request and receive the selected filefrom either the working device 120 or the remote storage 460.

FIGS. 46A-B may also illustrate screens that may be displayed on thepersonal device 122, representing how different types of files from thedevice state 62 of the working device 120 or the partial device state572 residing on the remote storage 460 may be obtained on the personaldevice 122. Turning first to FIG. 46A, a user may select the simplifieddata transfer application icon 40 of the screen 642, which may cause thesimplified data transfer application may launch. As should beappreciated, upon the launch of the simplified data transferapplication, the personal device 122 may download the partial devicestate pointers 572 from the remote storage 460 and/or the device statepointers 208 from the working device 120.

As illustrated in FIG. 46B, the handheld device 40 may display a screen674 when the icon 40 is selected and the icon 650, labeled “Photos,” isalso selected. A corresponding series of list items 676 may representcategories of photos from the partial device state pointers 572 or thedevice state pointers 208. The button 655, labeled “Settings,” mayenable the user to enable certain settings, as described above withreference to FIG. 12. Selecting each list item 666 may cause thehandheld device 40 to correspondingly display lists of photos of theselected category, which may thereafter be downloaded in the mannerdescribed above.

FIGS. 47A-E may also illustrate screens that may be displayed on thepersonal device 122, representing how different types of files from thedevice state 62 of the working device 120 or the partial device state572 residing on the remote storage 460 may be obtained on the personaldevice 122. Turning first to FIG. 47A, a user may select the simplifieddata transfer application icon 40 of the screen 642, which may cause thesimplified data transfer application may launch. As should beappreciated, upon the launch of the simplified data transferapplication, the personal device 122 may download the partial devicestate pointers 572 from the remote storage 460 and/or the device statepointers 208 from the working device 120.

As illustrated in FIG. 47B, the handheld device 40 may display a screen678 when the icon 40 is selected and the icon 652, labeled “Music,” isalso selected. A corresponding series of list items 680 may representplaylists of music from the partial device state pointers 572 or thedevice state pointers 208. The button 655, labeled “Settings,” mayenable the user to enable certain settings, as described above withreference to FIG. 12.

Selecting the list item 680 labeled “Purchased” may cause the handhelddevice 40 to display a screen 682, as illustrated in FIG. 47C. Thescreen 682 may include list items 684 representing purchased media filesthat may reside on either the remote storage 460 or the working device120. A button 684 may enable the user to navigate back to the screen 644of FIG. 47B. When the user selects a song from among the list items 684,the personal device 122 may request and receive the selected file fromeither the working device 120 or the remote storage 460. By way ofexample, the user may select the list item 684 labeled “The CosmicGate.” In response, the personal device 122 may download or stream thecorresponding media file.

As illustrated by a screen 688 of FIG. 47D, the selected presentationfile may thereafter be playable on the personal device 122. On thescreen 688, a button 684 may enable the user to navigate back to thescreen 682 of FIG. 47C. If a user selects a button 690 of the screen688, the personal device 122 may display a screen 692, as illustrated inFIG. 47E. The screen 692 may include a button 694, labeled “Save Song.”Selecting the button 694 may enable the user to save the media file ontothe personal device 122. It should be appreciated that saving the mediaonto the personal device 122 may involve storing the file in thenonvolatile storage 16, such that the file may remain on the personaldevice 122 after the connection to either the working device 120 or theremote storage 460 has terminated. It should further be appreciated thatany file received onto the personal device 122 may be saved in thismanner from each native application that receives such files. Forexample, a photo application may enable saving received photos into thenonvolatile storage 16 in the manner music files may be saved, asdescribed above.

It should be appreciated that the functionality provided by the softwaredescribed in FIGS. 44-47 may be implemented in a variety of ways. Forexample, rather than include all of the above-described functionality ina single data transfer application on the personal device 122, thefunctionality may be distributed across many applications. Thus, anapplication associated with each type of file that may be retrieved mayindividually provide interaction with the remote storage 460 or theworking device 120. For example, a photo management application on thepersonal device 122 may include a library called “Recently Viewed on MyDesktop.” Selecting the library may initiate the simplified datatransfer to obtain from the remote storage 460 or the working device 120an index of all photos recently viewed on the working device 120 and/orautomatically transfer all or some of the photos. As should beunderstood, a media management application on the personal device 122,such as iPod®, may provide similar functionality relating to media filesfrom the working device 120; a web browser on the personal device 122,such as Safari®, may provide similar functionality relating to web pagesfrom the working device 120; and/or productivity software on thepersonal device 122, such as Keynote® or iWork®, may provide similarfunctionality relating to documents from the working device 120.

One or more specific embodiments of the present disclosure are describedabove. In an effort to provide a concise description of theseembodiments, not all features of an actual implementation are describedin the specification. It should be appreciated that in the developmentof any such actual implementation, as in any engineering or designproject, numerous implementation-specific decisions must be made toachieve the developers' specific goals, such as compliance withsystem-related and business-related constraints, which may vary from oneimplementation to another. Moreover, it should be appreciated that sucha development effort might be complex and time consuming, but wouldnevertheless be a routine undertaking of design, fabrication, andmanufacture for those of ordinary skill having the benefit of thisdisclosure.

What is claimed is:
 1. A method comprising: providing a first userprompt on a first electronic device when a near field communicationinterface of the first electronic device is proximate to a near fieldcommunication interface of a second electronic device, wherein the firstuser prompt provides an option to transfer at least one of all user datafiles currently open in a plurality of applications running on thesecond electronic device, the first user prompt being independent fromeach of the applications that opens a user data file, the first userprompt indicating that the first electronic device can receive only userdata files currently open on the second user device, the firstelectronic device being different from the second electronic device;communicating a request from the first electronic device to the secondelectronic device to send the at least one of the open user data fileswhen the option is selected; receiving data associated with the at leastone of the open user data files in the first electronic device; andproviding a second user prompt on the first electronic device, whereinthe second user prompt provides an option to open, on the first device,the at least one of the user data files currently open on the secondelectronic device, the second user prompt being independent from each ofthe applications that opens a user data file.
 2. The method of claim 1,wherein the plurality of applications running on the second electronicdevice comprises a web browser, a spreadsheet application, apresentation application, a media management application, a gamingplatform, a document editing application, a photo managementapplication, or a file backup application, or any combination thereof.3. The method of claim 1, wherein receiving the at least one of the openuser data files comprises receiving the at least one of the open userdata files in its entirety when the at least one of the open user datafiles is smaller than a threshold size and receiving only a portion ofthe at least one of the open user data files when the at least one ofthe open user data files is larger than the threshold size.
 4. Themethod of claim 1, wherein receiving the at least one of the open userdata files comprises receiving the at least one of the open user datafiles in its entirety when the at least one of the open user data filesis smaller than a threshold size and receiving only a pointer describingthe at least one of the open user data files when the at least one ofthe open user data files is larger than the threshold size.
 5. Themethod of claim 4, wherein the second user prompt provides an option todownload the at least one of the open user data files based at least inpart on the pointer when the at least one of the open user data files islarger than the threshold size.
 6. The method of claim 1, whereinproviding the second user prompt comprises providing a primarilytext-based prompt or a primarily image-based prompt.
 7. The method ofclaim 1, wherein providing the first user prompt is triggered by thefirst electronic device tapping the second electronic device.
 8. Amethod comprising: establishing near field communication between a firstelectronic device and a second electronic device when the firstelectronic device is proximate to the second electronic device;receiving identification information from the first electronic device inthe second electronic device via the near field communication; receivingnetwork configuration information from the first electronic device inthe second electronic device via the near field communication;establishing network communication between the first electronic deviceand the second electronic device based at least in part on the networkconfiguration information; receiving in the second electronic device arequest for data transfer to the first electronic device from the secondelectronic device via the network communication, wherein the request fordata transfer comprises a request to transfer only open user data filesassociated with a plurality of applications currently open on the secondelectronic device, the request being received from a source on the firstdevice, the source being different from each of the applications; andtransferring data associated with all of the open user data filesassociated with the plurality of applications currently open on thesecond electronic device from the second electronic device to the firstelectronic device via the network communication.
 9. The method of claim8, wherein transferring the data comprises transferring a list of all ofonly open user data files associated with the plurality of applicationscurrently open on the second electronic device to the first electronicdevice.
 10. The method of claim 9, wherein the request for data transfercomprises a request identifying the plurality of applications from whichto transfer user data files.
 11. A method comprising: establishingnetwork communication between a first electronic device and a secondelectronic device, wherein the first electronic device includes dataopen on a plurality of open applications running on the first electronicdevice; in response to a tapping of the first electronic device on thesecond electronic device, providing a prompt on the second electronicdevice with an option to initiate a file transfer activity between thefirst electronic device and the second electronic device; communicatinga request from the second electronic device to the first electronicdevice via the network communication to initiate the file transferactivity when the option to initiate the file transfer activity isselected, the request being provided from outside of each of the openapplications; and receiving in the second electronic device only thedata open in a topmost application of the plurality of open applicationsrunning on the first electronic device via the network communication inresponse to the request to initiate the file transfer activity.
 12. Themethod of claim 11, wherein establishing the network communicationcomprises establishing a peer-to-peer personal area network connection,a peer-to-peer local area network connection, or a peer-to-peerconnection over the Internet, or a combination thereof.
 13. A methodcomprising: providing a prompt on a first electronic device with anoption to establish communication with a second electronic device andinitiate a file transfer activity, wherein the second electronic deviceincludes data open on a plurality of open applications, the prompt beingindependent from each of the applications that opens a user data file,the file transfer activity to be triggered by the first electronicdevice and being configured to transfer only open files from the secondelectronic device to the first electronic device; establishingcommunication between the first electronic device and the secondelectronic device when the option to establish communication andinitiate the file transfer activity is selected; communicating a requestfrom the first electronic device to the second electronic device toinitiate the file transfer activity, the request being provided fromoutside of each of the open applications; and receiving in the firstelectronic device only the data open in a topmost application of theplurality of open applications running on the second electronic device.14. The method of claim 13, wherein establishing communication betweenthe first electronic device and the second electronic device comprisesestablishing communication over a peer-to-peer personal area networkconnection, a peer-to-peer local area network connection, or apeer-to-peer connection over the Internet, or a combination thereof.